Closed
Bug 337004
Opened 20 years ago
Closed 19 years ago
style definitions in select and option appear to be interpreted backwards
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
INCOMPLETE
People
(Reporter: scratch65536, Unassigned)
Details
(Whiteboard: CLOSEME 06/27)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3
Intuitively, setting font-size in the <select>'s style tag (class seems not to be being interpreted at all--see bug 337001) should size the <select>'s window, while setting font-size in the <option>'s style tag should size the font being displayed. But it currently works exactly the other way around: setting fontsize in <option> sizes the window; setting it in <select> sizes the displayed font, though poorly (I'll report that elsewhere).
I've not tried to see whether other characteristics are similarly backwards.
Reproducible: Always
Steps to Reproduce:
1. create a <select> list and apply dissimilar style="font-size:..." to the <select> and its <option>s.
2.
3.
Actual Results:
I became momentarily quite confused :-)
I only have the default theme loaded.
| Reporter | ||
Comment 1•20 years ago
|
||
It turns out to be a bit more complicated than I thought, though not more intuitive.
Setting the fontsize in the <select> modifies the font as shown in the <select>'s window, but not the size of the <select>'s window itself nor the font size shown in the list's window.
Setting the fontsize in the <option> modifies the window size, and the size shown in the open list's window, but not the size shown in the <select>'s window.
Comment 2•19 years ago
|
||
Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!
Whiteboard: CLOSEME 06/27
Version: unspecified → 1.5.0.x Branch
Comment 3•19 years ago
|
||
No response from reporter re: comment 2 -->INCOMPLETE.
Reporter, if you still see this problem with the latest release of Firefox 2, please reopen this bug. Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•