Summary: | [testcase] <option> CSS "width" doesn't work | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Iñaki Baz Castillo <ibc> |
Component: | khtml | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | browserbugs2, samuel.brack, zahl |
Priority: | NOR | ||
Version: | 3.5 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Web page showing the issue |
Description
Iñaki Baz Castillo
2007-06-10 02:12:30 UTC
I have created a simple HTML code to show the problem. It's here: http://ibc.43i.net/khtml-select-width-issue/index.html Sorry, the link is wrong. This is the correct one: http://ibc.43i.net/khtml-select-width-issue.html If the above link fails (because the free web hosting that deletes the content) I attach the page that show the problem. Created attachment 21376 [details]
Web page showing the issue
Please, any comment about this issue? really nobody confirms it at least? I think it's very obvious that the bug does exist. Thanks. Confirmed on 3.5.8, but seems to be fixed in 4.0 beta4. The bug still exists in Suse KDE4 live CD: KDE 4.0 RC2 (3.97.0) I'm not sure if 4.0beta4 is higher than RC2 3.97.0. This is **not** fixed in KDE 4.0.1 of Kubuntu. Sadly, this still exists in 4.0 branch r793993. Still occurs in KDE 4.2.2. Hello all,
I loaded attachment 21376 [details] in Konqueror 4.4.3 (Linux 2.6.31-19-generic i686 32bits; Kubuntu package; Qt 4.6.2) and when expanded, the list of options was as wide as its widest option (the 2nd option which was obviously wider than 50px). No clipping occured. So, as far as I can see, this bug was FIXED. Otherwise this WORKSFORME.
Note that the testcase has invalid document structure (document root and body node are inferred), no doctype declaration; so it triggers "quirks" backward-compatible rendering mode, not standards compliant rendering mode. Also, the style="width: 100%" for the option is totally, entirely pointless, irrelevant if the webpage uses valid code and declares a doctype triggering standards compliant rendering mode. So, the problem could/would have been fixed just by upgrading the markup code to begin with.
regards, Gérard
Fixed in 4.5.4, closing this report. |