Closed
Bug 1270494
Opened 8 years ago
Closed 8 years ago
Autocomplete suggestions for multiple values in ruleview appear in the wrong place
Categories
(DevTools :: Inspector: Rules, defect, P3)
Tracking
(firefox47 unaffected, firefox48 wontfix, firefox49 wontfix, firefox50 fixed)
RESOLVED
FIXED
Firefox 50
Tracking | Status | |
---|---|---|
firefox47 | --- | unaffected |
firefox48 | --- | wontfix |
firefox49 | --- | wontfix |
firefox50 | --- | fixed |
People
(Reporter: arni2033, Assigned: jdescottes)
References
Details
(Keywords: regression)
Attachments
(1 file)
>>> My Info: Win7_64, Nightly 49, 32bit, ID 20160504043118 STR: 1. Open inspector -> rule view 2. Click on string "element {" to start editing new rule 3. Type "background", press Tab key, type "darkolivegreen" 4. Press Spacebar AR: Autocomplete list appears attached to the beginning of the value "darkolivegreen !important" ER: Autocomplete list should appear attached to the beginning of autocompleted string "!important" This is minor regression from bug 1168246. Regression range: > https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=dbb64aae2a239d1ae85a6591a57058ad29ab90e7&tochange=484cdaff31215bf625eb0616247a9d77ad5e1147
Updated•8 years ago
|
Priority: -- → P3
Happens with every "multiple" value, e.g.: "background: gray linear-gradient(to right, gray, gray) repeat scroll 100% 100% !important;"
Summary: Autocomplete suggestions for "!important" in ruleview appear in the wrong place → Autocomplete suggestions for multiple values in ruleview appear in the wrong place
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → jdescottes
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•8 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/57882/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/57882/
Assignee | ||
Comment 3•8 years ago
|
||
Try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=62ec25b8d84d
Assignee | ||
Comment 4•8 years ago
|
||
Comment on attachment 8760200 [details] Bug 1270494 - fix autocomplete popup offset for multiple values input; Review request updated; see interdiff: https://reviewboard.mozilla.org/r/57882/diff/1-2/
Attachment #8760200 -
Attachment description: Bug 1270494 - fix autocomplete popup offset for multiple values input → Bug 1270494 - fix autocomplete popup offset for multiple values input;
Attachment #8760200 -
Flags: review?(pbrosset)
Comment 5•8 years ago
|
||
Comment on attachment 8760200 [details] Bug 1270494 - fix autocomplete popup offset for multiple values input; https://reviewboard.mozilla.org/r/57882/#review55298 - The test works fine and quickly. - The bug described in comment 0 appears to be fixed. - When the input switches to multi-line though, there's no offset anymore. Do we not want to fix this case? Should it be a separate bug? In any case, I think we should ship this. ::: devtools/client/shared/test/browser_inplace-editor_autocomplete_offset.js:16 (Diff revision 2) > + > +// Test the inplace-editor autocomplete popup is aligned with the completed query. > +// Which means when completing "style=display:flex; color:" the popup will aim to be > +// aligned with the ":" next to "color". > + > +const testData = [ Please add a comment here to explain what the structure of this data array should be.
Attachment #8760200 -
Flags: review?(pbrosset) → review+
Assignee | ||
Comment 6•8 years ago
|
||
Comment on attachment 8760200 [details] Bug 1270494 - fix autocomplete popup offset for multiple values input; Review request updated; see interdiff: https://reviewboard.mozilla.org/r/57882/diff/2-3/
Assignee | ||
Comment 7•8 years ago
|
||
https://reviewboard.mozilla.org/r/57882/#review55298 Fixing it for the multiline case requires to change the way we calculate the left indent, because we cannot easily predict when the line breaks. I will try to play with another way to measure the indent. If it is straightforward enough I will push it here otherwise I will create a separate bug. > Please add a comment here to explain what the structure of this data array should be. done, also fixed in browser_inplace-editor_autocomplete_01.js & browser_inplace-editor_autocomplete_02.js
Comment hidden (spam) |
Assignee | ||
Comment 9•8 years ago
|
||
Rebased and pushed to try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=b2466bd33e10 I logged Bug 1278789 for handling the multiline case. I'm confident this can be handled with the approach I described in Bug 1278789 comment 1, but this is out of scope of this bug so I prefer to handle this separately.
See Also: → 1278789
Comment 10•8 years ago
|
||
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/fx-team/rev/daadc8567a11 fix autocomplete popup offset for multiple values input;r=pbro
Comment 11•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/daadc8567a11
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox50:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 50
Comment 12•8 years ago
|
||
Should we consider uplifting this?
status-firefox47:
--- → unaffected
status-firefox48:
--- → affected
status-firefox49:
--- → affected
Flags: needinfo?(jdescottes)
Version: unspecified → 48 Branch
Assignee | ||
Comment 13•8 years ago
|
||
This is a minor positioning issue, not worth uplifting in my opinion.
Flags: needinfo?(jdescottes)
Comment 14•8 years ago
|
||
I have reproduced this bug with Nightly 49.0a1 (2016-05-05) on Windows 7, 64 Bit! The bug's fix is now verified on latest Nightly 50.0a1. Build ID 20160722030235 User Agent Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0
QA Whiteboard: [bugday-20160722]
Comment 15•7 years ago
|
||
Reproduced this bug in firefox nightly 49.0a1 (2016-05-05) as comment 0 with ubuntu 16.04 (64 bit) Verified this bug as fixed with latest firefox nightly 50.0a1 (Build ID: 20160801030227) Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0
QA Whiteboard: [bugday-20160722] → [bugday-20160722] [bugday-20160803]
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•