Bug 68659 - A calc cell with a linked element to HTML_1 gets no row/column reference in a formula.
Summary: A calc cell with a linked element to HTML_1 gets no row/column reference in a...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2013-08-28 12:54 UTC by kris.vanbroeck
Modified: 2014-08-04 16:15 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:

example (11.63 KB, application/vnd.oasis.opendocument.spreadsheet)
2013-08-28 13:38 UTC, kris.vanbroeck

Note You need to log in before you can comment on or make changes to this bug.
Description kris.vanbroeck 2013-08-28 12:54:59 UTC
A reference to a cell wich contains a linked element in HTML_1 doesn't work anymore, it worked in LO-version 4.0.3 (Win7 Home, 64bit)
The cell contents is visible, but the contents has/gets no Row/Column reference, so the cell can't be referenced by another cell/formula.

some keywords and links:
Link to External Data, Web Page Query filter, "HTML_table1"
Comment 1 kris.vanbroeck 2013-08-28 13:38:32 UTC
Created attachment 84794 [details]
Comment 2 kris.vanbroeck 2013-08-28 14:25:05 UTC
Same problem with other sorts of direct formatting,
e.g. link to: email address, url ...
Comment 3 Dominique Boutry 2013-10-22 13:09:21 UTC
Can't reproduce this case with LibO on Win7 : I copied [A1:C18] in [E1:G18] with "Link" (special paste > Linked) in your attachment, all works.
Comment 4 Dominique Boutry 2013-12-07 15:49:45 UTC
Additional investigations with LibO béta2 on Win7 :

When you say "the contents has/gets no Row/Column reference", I understand :
- a single left clic on the cell content doesn't select the cell, its reference is not displayed in the window header as usual,
- OR click in B11 then type "=" then click in B4 : doesn't results in "=B4" in B11

I can see that clicking on the link itself does nothing ; clicking on the remaining of the cell drives the correct behaviour.

Please let us know if it is your question, and if I answered it
Comment 5 Jean-Baptiste Faure 2013-12-14 12:33:16 UTC
Due to the question in comment#4, set the status to NEEDINFO

Best regards. JBF
Comment 6 QA Administrators 2014-07-08 17:29:18 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

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

Warm Regards,
QA Team
Comment 7 QA Administrators 2014-08-04 16:15:20 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO