WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED INVALID
33177
[Qt] View content in iframe - shows borders when it shouldn't
https://bugs.webkit.org/show_bug.cgi?id=33177
Summary
[Qt] View content in iframe - shows borders when it shouldn't
Vikram
Reported
2010-01-04 12:40:36 PST
STEPS TO REPRODUCE: 1. Open
http://waplabdc.nokia-boston.com/browser/users/html/html_iframes/iframe_frameborder_2.html
2. Now see the result ACTUAL RESULTS: According to the test case frame no 2 and 3 should not have borders but it is showing borders EXPECTED RESULTS: Only 1st frame has border other 2 and 3 should not have.
Attachments
supporting image
(41.58 KB, image/jpeg)
2010-01-04 12:41 PST
,
Vikram
no flags
Details
Supporting image 2
(38.41 KB, image/jpeg)
2010-01-04 12:42 PST
,
Vikram
no flags
Details
supporting image 3
(41.77 KB, image/jpeg)
2010-01-04 12:42 PST
,
Vikram
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Vikram
Comment 1
2010-01-04 12:41:49 PST
Created
attachment 45818
[details]
supporting image
Vikram
Comment 2
2010-01-04 12:42:23 PST
Created
attachment 45819
[details]
Supporting image 2
Vikram
Comment 3
2010-01-04 12:42:45 PST
Created
attachment 45820
[details]
supporting image 3
Vikram
Comment 4
2010-01-04 12:43:30 PST
Internally linked to -
https://qtrequirements.europe.nokia.com/browse/BR-1119
mario borges
Comment 5
2010-01-20 09:56:57 PST
From the HTML spec: ---------------------------- The frameborder attribute specifies whether or not to display a border around an iframe. Value Description 1 Border on (this is default) 0 Border off ---------------------------- In this test case, the frameborder value for the 2nd and 3rd iframes are set to "20" and "-1". Internet Explorer interprets those values and a non-1 value so it turns the borders off. The other browsers (wekbit, safari, firefox) interprets those values and as a non-0 value so it defaults to borders on. Since the spec states that the Border on value is the default value then it would make sense to assume that ANY value other than zero should be interpreted as the default value of border on. Therefore, I propose to dismiss this bug and no further action taken for it.
Tor Arne Vestbø
Comment 6
2010-03-05 09:39:40 PST
Please follow the QtWebKit bug reporting guidelines when reporting bugs. See
http://trac.webkit.org/wiki/QtWebKitBugs
Specifically: - The 'QtWebKit' component should be used for bugs/features in the public QtWebKit API layer, not to signify that the bug is specific to the Qt port of WebKit
http://trac.webkit.org/wiki/QtWebKitBugs#Component
Robert Hogan
Comment 7
2010-03-16 10:49:14 PDT
Konqueror shows borders on the second and not the third (so off if you're 0 or less, on if you're 1 or more). Opera matches Internet Explorer's behaviour. So we have a tie and in such situations Konqueror traditionally has the casting vote. ;-) In the absence of a valid value in frameborder the default value must apply - so gecko/webkit (and Mario) are correct I think.
http://validator.w3.org/check?uri=http://waplabdc.nokia-boston.com/browser/users/html/html_iframes/iframe_frameborder_2.html&charset=(detect+automatically)&doctype=Inline&group=0
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug