Width of a text block with monospace font is miscalculated if a word-spacing is specified. This leads to rendering bugs if more than one block appears on a line.
Created attachment 2731 [details] Testcase Simple, minimal testcase
Created attachment 2732 [details] Patch to correct output Okay this should work
Are you adding in the word-spacing with every space encountered? What if someone types "A[space] [space][space]B"?
Test in Firefox.
(In reply to comment #3) > Are you adding in the word-spacing with every space encountered? What if someone types "A[space] > [space][space]B"? > It should be fine, by the time we calculate hte width of text blocks all the extraneous white space ha been removed.
Created attachment 2733 [details] über-test-case
Created attachment 2735 [details] screenshot of firefox behavior
Okay the current patch borks when a comment is placed in whitespace, in a monospace text block. Looking at the rendertree a the leading space following the comment is not being removed -- it is if the font is not monospaced. The fact that this is only in monospace makes me hope it will be reasonably easy to find... ho hum... this irks me..
I think this bug is fixed with the patch... am going to open another bug covering the comment issue.
spurious spacing around comment tags is due to the use of pre tags rather than font-family: monospace; I'm going to do a few checks but i think the current patch is in fact correct.
*** This bug has been marked as a duplicate of 3692 ***