Closed
Bug 907244
Opened 12 years ago
Closed 12 years ago
[MP] Defect - Opening a new tab when the page has focus doesn't correctly focus the location bar
Categories
(Firefox for Metro Graveyard :: Input, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
Firefox 26
People
(Reporter: cwiiis, Assigned: rsilveira)
References
Details
(Whiteboard: [preview] feature=defect c=tbd u=tbd p=1)
Attachments
(2 files, 1 obsolete file)
1.04 KB,
patch
|
mbrubeck
:
review+
|
Details | Diff | Splinter Review |
4.16 KB,
patch
|
mbrubeck
:
review+
|
Details | Diff | Splinter Review |
If you browse to a page, click/touch in the page, then open a new tab with ctrl+t, the location bar appears to be focused, but does not actually hold focus (it's highlighted orange, but no cursor and typing doesn't work)
Updated•12 years ago
|
Blocks: metrov1backlog
Summary: Opening a new tab when the page has focus doesn't correctly focus the location bar → Defect - Opening a new tab when the page has focus doesn't correctly focus the location bar
Whiteboard: [preview-triage] feature=defect c=tbd u=tbd p=0
Updated•12 years ago
|
Blocks: MetroPreviewRelease
Summary: Defect - Opening a new tab when the page has focus doesn't correctly focus the location bar → [MP] Defect - Opening a new tab when the page has focus doesn't correctly focus the location bar
Whiteboard: [preview-triage] feature=defect c=tbd u=tbd p=0 → [preview] feature=defect c=tbd u=tbd p=0
Comment 1•12 years ago
|
||
Currently, the thing that gets highlighted is a xul box around the input, it's possible for that to get out of sync with the input. We need to look at making sure the editing state gets set and unset at all of the right times.
Alternately, we could just get rid of editing state and use CSS4 parent selectors (but I forget whether we implement those right now...).
Assignee | ||
Comment 2•12 years ago
|
||
We're setting the focus while the navbar was not visible.
Assignee: nobody → rsilveira
Status: NEW → ASSIGNED
Comment 3•12 years ago
|
||
Hi Rodrigo, can you provide a point estimate for this defect.
Flags: needinfo?(rsilveira)
Priority: -- → P2
QA Contact: jbecerra
Assignee | ||
Updated•12 years ago
|
Flags: needinfo?(rsilveira)
Whiteboard: [preview] feature=defect c=tbd u=tbd p=0 → [preview] feature=defect c=tbd u=tbd p=1
Assignee | ||
Comment 4•12 years ago
|
||
Attachment #795772 -
Attachment is obsolete: true
Attachment #796070 -
Flags: review?(mbrubeck)
Comment 5•12 years ago
|
||
Comment on attachment 796070 [details] [diff] [review]
Patch v2
Could you add a test for this too (maybe in browser_contextui.js)?
Attachment #796070 -
Flags: review?(mbrubeck) → review+
Assignee | ||
Comment 6•12 years ago
|
||
Verified that it failed without the fix.
Attachment #796190 -
Flags: review?(mbrubeck)
Updated•12 years ago
|
Attachment #796190 -
Flags: review?(mbrubeck) → review+
Assignee | ||
Comment 7•12 years ago
|
||
Comment 8•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/77e25cd0d80e
https://hg.mozilla.org/mozilla-central/rev/17e8229405fe
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → Firefox 26
Comment 9•12 years ago
|
||
Verified as fixed, with the latest Nightly (build ID: 20130915030208), for iteration #14, on Win 8 64bit, by following the STR from comment 0.
I think this also needs some device verification.
Status: RESOLVED → VERIFIED
Comment 10•11 years ago
|
||
Went through the following "Defect" for iteration #15 (touch device verification) without issues. Used the following build:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013-10-15-03-03-19-mozilla-central/
- Went through the original defect described in comment #0 without any issues
- Ensured that the URL bar was selected with a cursor when using the CTRL + T method
- Ensured that the URL bar was selected with a cursor when using the "+" button in the "Tab App Bar"
- Ensured that the URL bar was selected with a cursor when using the junior style button
- Went through all of the above test cases in filled and full views without issues
You need to log in
before you can comment on or make changes to this bug.
Description
•