Bug 41583 – Repaint missed when adding a class to an element created by surrounding a range

• Component: Layout and Rendering
• Status: RESOLVED FIXED

[Nate Whetsell]

Created attachment 60477 [details]
Test document

The test document consists of the word "test" in three places at the beginning and end of some lorem ipsum text. The occurrences of "test" are highlighted using a CSS style. The first occurrence starts out with a shadow (also a CSS style). Pressing the "Next" and "Previous" buttons should move the shadow to the other occurrences.

Apparently, pressing Next once after the document loads does move the shadow to the next "test", it is just not being repainted. On a Mac, switching to another application and then switching back to Safari will show the shadow as expected.

This appears to have something to do with the lines on which the "test" strings appear. If all three "test" strings appear on the same line, the shadow is painted as expected. Also, the second "test" string is enclosed in a <span> with some whitespace at the end, literally <span>test </span>. Eliminating the whitespace (or the <span>) also results in expected repaint behavior. Finally, the spans used for the highlighting and shadows are created by enclosing range objects; they aren't part of the markup on loading. If these spans are made part of the markup, repainting occurs as expected.

Expected repainting behavior occurs in Firefox and (strangely) Google Chrome.

[Nate Whetsell]

 The last Mac OS X nightly build where I can reproduce the bug is r83010. The bug is fixed in r83080.

Thanks for the update. This must have been fixed in http://trac.webkit.org/changeset/83075