[chromium-bugs] Issue 104 in chromium: Suboptimal perfomance on Google Mail standard interface

2008-11-21 Thread codesite-noreply
Updates: Status: Upstream Labels: Mstone-1.1 Comment #12 on issue 104 by [EMAIL PROTECTED]: Suboptimal perfomance on Google Mail standard interface http://code.google.com/p/chromium/issues/detail?id=104 (No comment was entered for this change.) -- You received this message be

[chromium-bugs] Issue 104 in chromium: Suboptimal perfomance on Google Mail standard interface

2008-10-28 Thread codesite-noreply
Issue 104: Suboptimal perfomance on Google Mail standard interface http://code.google.com/p/chromium/issues/detail?id=104 Comment #11 by [EMAIL PROTECTED]: reported upstream: https://bugs.webkit.org/show_bug.cgi?id=21938 -- You received this message because you are listed in the owner or CC

[chromium-bugs] Issue 104 in chromium: Suboptimal perfomance on Google Mail standard interface

2008-10-28 Thread codesite-noreply
Issue 104: Suboptimal perfomance on Google Mail standard interface http://code.google.com/p/chromium/issues/detail?id=104 Comment #10 by [EMAIL PROTECTED]: This is a webkit bug, which we should report upstream. (It may already be on file.) I think it is tangentially related to https://bugs.w

[chromium-bugs] Issue 104 in chromium: Suboptimal perfomance on Google Mail standard interface

2008-10-21 Thread codesite-noreply
Issue 104: Suboptimal perfomance on Google Mail standard interface http://code.google.com/p/chromium/issues/detail?id=104 Comment #9 by [EMAIL PROTECTED]: Yes, still an issue, we haven't made any change to address this. Darin is the right person to explain the precise optimization here. Issu

[chromium-bugs] Issue 104 in chromium: Suboptimal perfomance on Google Mail standard interface

2008-10-21 Thread codesite-noreply
Issue 104: Suboptimal perfomance on Google Mail standard interface http://code.google.com/p/chromium/issues/detail?id=104 Comment #8 by [EMAIL PROTECTED]: I can't see a performance difference between 0.3.155.0 and Firefox. I wonder if this is still an issue. Please re-validate this bug with a