Hi, there seems to be a bug in webkit (affecting webkitgtk, qtwebit and chromium) which leads to incorrect rendering of: http://www.flumotion.com/first_webm_live_event.php I can reproduce it with midori (webkitgtk), arora (qtwebkit) and chromium, haven't tried anything else. Looks like the problem lies in interpretation of align=center inside table element. It behaves differently from what I'd expect after trying other options (like align=left or align=right) and it is different from firefox. The reason I'm asking here first before filling a bug is to be 100 % sure it's a bug in webkit and not in the above mentioned page +firefox... webkitgtk is 1.2.3, qtwebkit is the one shipped with 4.6.3 (arora says it's webkit 532.4) and chromium 6.0.476.0 (0). Martin
A reduction would be useful. My general approach is: file a bug first, ask questions later. :) Once we have a bug, we can attach a reduction and work towards resolution (even if that means no change to WebKit). -eric On Mon, Aug 23, 2010 at 3:06 PM, Martin Sourada <martin.sourada@gmail.com> wrote:
Hi,
there seems to be a bug in webkit (affecting webkitgtk, qtwebit and chromium) which leads to incorrect rendering of: http://www.flumotion.com/first_webm_live_event.php
I can reproduce it with midori (webkitgtk), arora (qtwebkit) and chromium, haven't tried anything else.
Looks like the problem lies in interpretation of align=center inside table element. It behaves differently from what I'd expect after trying other options (like align=left or align=right) and it is different from firefox. The reason I'm asking here first before filling a bug is to be 100 % sure it's a bug in webkit and not in the above mentioned page +firefox...
webkitgtk is 1.2.3, qtwebkit is the one shipped with 4.6.3 (arora says it's webkit 532.4) and chromium 6.0.476.0 (0).
Martin
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
On Mon, 2010-08-23 at 15:09 -0700, Eric Seidel wrote:
A reduction would be useful.
My general approach is: file a bug first, ask questions later. :)
Once we have a bug, we can attach a reduction and work towards resolution (even if that means no change to WebKit).
https://bugs.webkit.org/show_bug.cgi?id=44462 Reduction: https://bug-44462-attachments.webkit.org/attachment.cgi?id=65173 Not sure if this reduction is good enough, but at least it's rather small and shares the (probably) broken behaviour. Hope that helps. Thanks, Martin
participants (2)
-
Eric Seidel
-
Martin Sourada