Closed
Bug 1091324
Opened 11 years ago
Closed 11 years ago
Vertical scrollbar of the in-content preferences gets clipped when the window is short
Categories
(Firefox :: Settings UI, defect)
Firefox
Settings UI
Tracking
()
RESOLVED
DUPLICATE
of bug 1036434
People
(Reporter: jaws, Unassigned)
Details
Attachments
(1 file)
|
71.45 KB,
image/png
|
Details |
See screenshot.
I think this is the fault of the <stack> that is used.
It sounds like a lot of work, but I think the real solution here is to ditch the <stack> and the two direct children and replace them with HTML. We don't need the <stack> for showing and hiding the panes, as we already do that with hidden="true". The subdialog is shown via visiblity:visible/hidden; so that also doesn't necessitate the <stack>.
| Reporter | ||
Comment 1•11 years ago
|
||
Well, this can be a wormhole. Changing all of the in-content prefs to be based off of an XHTML document is going to be a lot of work. Some widgets, such as <xul:richlistbox> use document.commandDispatcher which is only available in XUL documents (bug 329394 comment #2).
Maybe there is something that can be done with the current XUL styling to get this to work without doing a wholesale refactoring? Dao, do you have any ideas?
Flags: needinfo?(dao)
Comment 2•11 years ago
|
||
(In reply to Jared Wein [:jaws] (please needinfo? me) from comment #0)
> Created attachment 8513954 [details]
> Screenshot of bug
>
> See screenshot.
>
> I think this is the fault of the <stack> that is used.
>
> It sounds like a lot of work, but I think the real solution here is to ditch
> the <stack> and the two direct children and replace them with HTML. We don't
> need the <stack> for showing and hiding the panes, as we already do that
> with hidden="true".
It sounds like the stack is redundant anyway and could be dropped without switching to HTML.
Flags: needinfo?(dao)
| Reporter | ||
Updated•11 years ago
|
No longer blocks: ship-incontent-prefs
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•