Observed both on Windows and Mac OS X.
I'm getting the same result from Firefox, but IE 7 works as expected.
On Windows, my copy of FF (2.0.6) does not have the problem. Neither does Opera on Windows. To the right of the second text input box, there are two buttons. On Safari on Windows, there is no room for the second button and it is pushed down, which , in turn, appears to push the table toward right (some interactions between 'float'd elements?). If you compare the width of two text input boxes (next to '帐号' and '密码'), Safari assigns noticeably larger values to them than FF, Opera and IE, which leaves smaller room for two image buttons.
I forgot to set the encoding to UTF-8 before posting. The second paragraph should read (set the encoding to UTF-8): If you compare the width of two text input boxes (next to '帐号' and '密码'), Safari assigns noticeably larger values to them than FF, Opera and IE, which leaves smaller room for two image buttons.
This looks fine to me, but maybe I'm not looking in the right place. The only problem I see with this page is mangled chars in the boxes along the left hand side. Some sort of encoding-auto-detection behavior in IE that this site is depending on I bet.
The site changed and this bug is not reproducible any more. The way Webkit calculates the width of a text field and a text area is still different from that of FF and IE and it breaks layouts in some Chinese web sites. Perhaps, a separate bug needs to be filed to track that issue (if not already filed).
(In reply to comment #5) > The site changed and this bug is not reproducible any more. The way Webkit > calculates the width of a text field and a text area is still different from > that of FF and IE and it breaks layouts in some Chinese web sites. Perhaps, a > separate bug needs to be filed to track that issue (if not already filed). It's helpful to have a local copy (or reduction) of pages for this very reason. Sometimes it's as easy as: - Saving a web page a "source" and adding a <base> tag (this method is still susceptible to the web site changing CSS or images or other resources, but may preserve enough to reproduce the bug) - Saving a webarchive of the original page (make sure the bug reproduces with no network connection, though, as webarchives don't always contain every resource they should) - Saving a web page as "Web page, complete" from Firefox, then loading it in Safari to make sure the issue reproduces (sometimes different content will be served to Firefox, which is why it's important to test the issue reproduces) Once you're sure the issue reproduces, attach the source file, the webarchive file, or a zip of the Firefox "web page, complete" files to the bug.