NEW 75691
Percentage height property is ignored for iframe
https://bugs.webkit.org/show_bug.cgi?id=75691
Summary Percentage height property is ignored for iframe
Mirela
Reported 2012-01-06 02:19:43 PST
Created attachment 121412 [details] Screenshot with iFrame rendering in WebKit vs. Safari I have the following html code which displays an iFrame: <!DOCTYPE html> <html> <head> <title></title> </head> <body> <iframe src="http://www.webkit.org/" style="height:100%; width:100%"></iframe> </body> </html> Even thought the iFrame style property "height" is 100%, the actual height of the iFrame is smaller than the height of the page(Image attached). This is an issue on the latest WebKit nightly build(r104196)on Windows and MAC. This is an issue in the latest Chrome too(16.0.912.75 m). This is not an issue in the latest Safari 5.1.2(7534.52.7).
Attachments
Screenshot with iFrame rendering in WebKit vs. Safari (203.42 KB, image/jpeg)
2012-01-06 02:19 PST, Mirela
no flags
test page (186 bytes, text/html)
2012-01-06 02:20 PST, Mirela
no flags
Mirela
Comment 1 2012-01-06 02:20:25 PST
Created attachment 121413 [details] test page
Alexey Proskuryakov
Comment 2 2012-01-06 10:45:50 PST
This changed in <http://trac.webkit.org/changeset/88913>. I don't know if it's a regression or improvement - Firefox behaves the same as WebKit nightlies. Does this cause issues on a live Web site?
Simon Fraser (smfr)
Comment 3 2012-01-06 11:06:36 PST
Does this affect elements other than iframes?
Simon Fraser (smfr)
Comment 4 2012-01-06 11:13:34 PST
Simon Fraser (smfr)
Comment 5 2012-01-06 11:24:54 PST
s/regressed/affected by. This might be expected behavior now.
Mirela
Comment 6 2012-01-13 05:55:14 PST
(In reply to comment #2) > This changed in <http://trac.webkit.org/changeset/88913>. > > I don't know if it's a regression or improvement - Firefox behaves the same as WebKit nightlies. Does this cause issues on a live Web site? This is not an issue on a live Web site. I have found this testing another bug reproduced only on Safari.
Note You need to log in before you can comment on or make changes to this bug.