Bug 123153 - DB links not detected properly
Summary: DB links not detected properly
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Hyperlink
  Show dependency treegraph
 
Reported: 2019-02-03 22:30 UTC by Frank Brütting
Modified: 2024-12-14 15:38 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Brütting 2019-02-03 22:30:59 UTC
Description:
`db:/…` text parts are detected as links, even if `db` is not on a word on its own (like in `example_db:/bla/blubb`).

Steps to Reproduce:
Write `example_db:/bla/blubb`, then press space or enter.

Actual Results:
The part `db:/bla/blubb` gets detected as a link.

Expected Results:
This link detection is wrong, as db is just the last part of `example_db` – hence it is not a `db/:` link.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Oliver Brinzing 2019-02-05 17:46:07 UTC
(In reply to zyklon87 from comment #0)
> Write `example_db:/bla/blubb`, then press space or enter.
> The part `db:/bla/blubb` gets detected as a link.

i can confirm this, but why, e.g. is 
"example_xx:/bla/blubb" not recognized as url at all?
Comment 2 Frank Brütting 2019-02-05 21:06:32 UTC
Maybe because it’s not a well-known (and thus useful) URL? I guess there is a whitelist.
Comment 3 QA Administrators 2021-02-05 04:11:25 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2023-02-06 03:19:19 UTC
Dear Frank Brütting,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug