Closed
Bug 1130007
Opened 10 years ago
Closed 10 years ago
in-content preferences: regression: misaligned homepage placeholder
Categories
(Firefox :: Theme, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox38 | --- | verified |
People
(Reporter: soeren.hentzschel, Assigned: Gijs)
References
Details
(Keywords: regression)
Attachments
(2 files)
(deleted),
image/png
|
Details | |
(deleted),
patch
|
jaws
:
review+
|
Details | Diff | Splinter Review |
There is a regression in the latest Nightly with the vertical alignment of the homepage label in the in-content preferences. Furthermore the input field has a different width compared with the select box above the homepage field.
Reporter | ||
Comment 1•10 years ago
|
||
"label" should read "placeholder text"…
Summary: in-content preferences: regression: misaligned homepage label → in-content preferences: regression: misaligned homepage placeholder
Assignee | ||
Comment 2•10 years ago
|
||
When did this last work?
Flags: needinfo?(cadeyrn)
Keywords: regression,
regressionwindow-wanted
Comment 3•10 years ago
|
||
I'm guessing bug 1038291 broke this, but I'm not sure.
Comment 4•10 years ago
|
||
This is because the textbox inside the table is now display: block and no more display: -moz-box. On Linux and Windows this change makes the text jumping 1px up, on OS X it's around 3px.
I could add a padding-top: 3px to fix this, but would this be okay and clean? Or is there a other solution?
Assignee | ||
Comment 5•10 years ago
|
||
(In reply to Richard Marti (:Paenglab) from comment #4)
> This is because the textbox inside the table is now display: block and no
> more display: -moz-box. On Linux and Windows this change makes the text
> jumping 1px up, on OS X it's around 3px.
>
> I could add a padding-top: 3px to fix this, but would this be okay and
> clean? Or is there a other solution?
Why can't we just make it display: -moz-box ?
Comment 6•10 years ago
|
||
(In reply to :Gijs Kruitbosch from comment #5)
>
> Why can't we just make it display: -moz-box ?
This was my first reaction too, but this didn't work (also with !important) it was still display: block.
Assignee | ||
Comment 7•10 years ago
|
||
(In reply to Richard Marti (:Paenglab) from comment #6)
> (In reply to :Gijs Kruitbosch from comment #5)
> >
> > Why can't we just make it display: -moz-box ?
>
> This was my first reaction too, but this didn't work (also with !important)
> it was still display: block.
It's because the parent (the table cell) is using display: flex. Why is that necessary?
I'll also note that this generally looks sloppy on OS X - the action dropdown for "When Nightly starts" and the buttons/textboxes below and above it are misaligned horizontally on the end side, for example.
Was this tested at all on OS X ? :-(
Depends on: 1038291
Flags: needinfo?(cadeyrn)
Assignee | ||
Updated•10 years ago
|
Keywords: regressionwindow-wanted
Priority: -- → P2
Comment 8•10 years ago
|
||
(In reply to :Gijs Kruitbosch from comment #7)
> (In reply to Richard Marti (:Paenglab) from comment #6)
> > (In reply to :Gijs Kruitbosch from comment #5)
> > >
> > > Why can't we just make it display: -moz-box ?
> >
> > This was my first reaction too, but this didn't work (also with !important)
> > it was still display: block.
>
> It's because the parent (the table cell) is using display: flex. Why is that
> necessary?
The flex is needed to stretch the cell to the whole width.
Assignee | ||
Comment 9•10 years ago
|
||
(In reply to Richard Marti (:Paenglab) from comment #8)
> (In reply to :Gijs Kruitbosch from comment #7)
> > (In reply to Richard Marti (:Paenglab) from comment #6)
> > > (In reply to :Gijs Kruitbosch from comment #5)
> > > >
> > > > Why can't we just make it display: -moz-box ?
> > >
> > > This was my first reaction too, but this didn't work (also with !important)
> > > it was still display: block.
> >
> > It's because the parent (the table cell) is using display: flex. Why is that
> > necessary?
>
> The flex is needed to stretch the cell to the whole width.
display: flex just sets it up to be a flex container. Considering that we're in XUL layout and you could just give the textbox -moz-box-flex (or attribute flex="1" or whatever), I still don't really understand why this is necessary.
Assignee | ||
Comment 10•10 years ago
|
||
(and anyway, if the table itself is forced to a certain width, cells normally fill up the space in the table... why is that not enough here?)
Comment 11•10 years ago
|
||
(In reply to :Gijs Kruitbosch from comment #9)
>
> display: flex just sets it up to be a flex container.
Yes, but the elements in this container are using flex-grow: 1; to have a working wrapping of the three buttons below.
> Considering that we're in XUL layout and you could just give the textbox
> -moz-box-flex (or attribute flex="1" or whatever), I still don't really
> understand why this is necessary.
Is this still a normal XUL layout with the table in it? It's not a grid, for why please read bug 1038291.
Comment 12•10 years ago
|
||
Can you look at setting width:100% on the menulist and then setting display:flex on the table cell that has the three buttons?
Assignee | ||
Comment 13•10 years ago
|
||
This works on OS X. I'll test Windows in a second.
Attachment #8560451 -
Flags: review?(jaws)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → gijskruitbosch+bugs
Status: NEW → ASSIGNED
Comment 14•10 years ago
|
||
Comment on attachment 8560451 [details] [diff] [review]
fix layout of general pane on OS X,
Review of attachment 8560451 [details] [diff] [review]:
-----------------------------------------------------------------
Yep, looks good on Windows.
Attachment #8560451 -
Flags: review?(jaws) → review+
Assignee | ||
Comment 15•10 years ago
|
||
Iteration: --- → 38.2 - 9 Feb
Points: --- → 1
Flags: qe-verify-
Flags: in-testsuite-
Flags: firefox-backlog+
Comment 16•10 years ago
|
||
display: -moz-box; and -moz-box-flex: 1; works as well (instead of display: flex; and flex-grow: 1;), plus it's adapted to xul.
Comment 17•10 years ago
|
||
Not when the buttons should wrap when the text in them is to wide.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
status-firefox38:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 38
Comment 19•10 years ago
|
||
Verified fixed on latest Nightly 39.0a1 (buildID: 20150317030206) and latest Aurora 38.0a2 (buildID: 20150316004007).
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•