Closed
Bug 7527
Opened 26 years ago
Closed 26 years ago
location bar and content selection aren't mutually exclusive
Categories
(Core :: DOM: Selection, defect, P3)
Core
DOM: Selection
Tracking
()
M11
People
(Reporter: cmaximus, Assigned: mjudge)
Details
Selection in the location field and selection in the content window aren't talking/listening to each other. In a happy world, they
should.
*To Repro
Select some text in the content window. Now select some text in the location control bar.
*Result
Even the not so keen observer will notice that both areas remain highlighted.
*Expected
What should happen is these two things should never be able to be selected at the same time. Selecting one should trigger
deselect on the other.
*Build info:
This bug is valid for 1999060108 for Mac/WinNT and 1999060208 for Linux
**there are 6 different ways to try this (location first, then content, vice versa, X3 platforms) the only one that works is if you
select some location field text and then some content area text on a MAC.
Per a request from Selection and Search component eng (mjudge) and qa (elig),
moving all "Selection and Search" bugs to new "Selection" component. Original
"Selection and Search" component will be retired.
Updated•26 years ago
|
QA Contact: claudius → elig
Comment 2•26 years ago
|
||
[QA Assigning to self.]
Comment 3•26 years ago
|
||
I'd hope the intended bug here is not to actually deselect the text but to
unhilite the selection. I'd expect that my selection hilite would reappear upon
regain of focus. Eli? Claudius?
set to M11
Target Milestone: M11
Reporter | ||
Comment 4•26 years ago
|
||
yes, exactly what you said. Some of the correct and/or Nova behavior is described in bug 7465. but I'll bow out now as this is Eli's
thang.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
Comment 6•26 years ago
|
||
These look the same to me, so rubber-stamping as duplicate.
Claudius, if you believe there are subtle differences (or relevant issues raised
within this bug report, but not within the other), could you please re-open this
bug, or append the relevant content into the other bug?
Thanks!
You need to log in
before you can comment on or make changes to this bug.
Description
•