RESOLVED FIXED 86090
Setting innerHTML for a "position: absolute" element does not update the rendered view
https://bugs.webkit.org/show_bug.cgi?id=86090
Summary Setting innerHTML for a "position: absolute" element does not update the rend...
Alexander Pavlov (apavlov)
Reported 2012-05-10 05:46:02 PDT
(From http://stackoverflow.com/questions/10534136/webkit-render-bug-for-dynamic-content) When I change the content of a span with javascript this change does not get rendered in Webkit browsers. This effect only applies when a wrapper span is positioned relative and the inner span is positioned absolute and has a fixed width and height. Here is the most simple example of the bug (check it in a webkit browser like Chrome or Safari) <!DOCTYPE HTML> <html> <head> <title>Webkit render bug</title> <style type="text/css"> .wrapper { position: relative; } #absolute-block { display: block; position: absolute; width: 152px; height:42px; background-color: #EEEE00; color: #FF0000; } </style> </head> <body> <h1>Webkit render bug</h1> <button onclick="document.getElementById('absolute-block').innerHTML = 'Update test';">Update test</button> <span class="wrapper"> Some content <span id="absolute-block">Absolute-block</span> </span> </body> </html> The click on the button will replace the content of the span in the DOM-tree but this doesn't get rendered by the webkit based browsers like Chrome and Safari. Other browsers do not have this render bug. Full FrameView invalidation fixes the issue.
Attachments
Test case (798 bytes, text/html)
2012-05-10 06:09 PDT, Alexander Pavlov (apavlov)
no flags
Alexander Pavlov (apavlov)
Comment 1 2012-05-10 06:09:09 PDT
Created attachment 141157 [details] Test case
Eric Seidel (no email)
Comment 2 2012-05-10 10:41:40 PDT
This feels a little like the a left-over-anonymous block bug which Jullien and Ojan and I were discussing the other day. Where you change a block to an inline and then try to change it back to a block and it doesn't reflow on the right line.
Ojan Vafai
Comment 3 2012-05-10 12:08:59 PDT
Yup. It sounds a lot like bug 74976.
Simon Fraser (smfr)
Comment 4 2016-03-04 11:04:51 PST
I can't reproduce this in recent nightly builds.
Note You need to log in before you can comment on or make changes to this bug.