NEW 35286
YUI: Button title copied to other buttons when going back to a page
https://bugs.webkit.org/show_bug.cgi?id=35286
Summary YUI: Button title copied to other buttons when going back to a page
Avery
Reported 2010-02-23 01:20:24 PST
Created attachment 49268 [details] This is the test file Steps to reproduce: 1) Load test.html. Note the names of the three buttons. 2) Type another URL into the location bar. 3) Hit back. 4) Note that one of the buttons now has the Kung Fu Panda name. Hitting forward and Back on Safari continues to propagate the name to the other controls. This does behavior does not occur in Firefox. I will also be filing a bug against YUI, since this bug does not occur when the javascript is inactive.
Attachments
This is the test file (2.62 KB, text/html)
2010-02-23 01:20 PST, Avery
no flags
Avery
Comment 1 2010-02-23 01:21:22 PST
Because of this bug, I am telling my client not to use Safari with my web-app since I fear that my client's users may hit the back button to get back to this page.
Avery
Comment 2 2010-02-23 01:26:31 PST
Note that removing the input name attribute makes this behavior go away.
Avery
Comment 3 2010-02-23 01:28:03 PST
The YUI bug is: 2528806
Mark Rowe (bdash)
Comment 4 2010-02-23 02:00:00 PST
The page loads several hundred kilobytes of JavaScript. It’s impossible for us to determine whether this is a bug in WebKit or in your JavaScript without spending a lot of time analyzing those hundreds of kilobytes of code. It’s as likely, if not more likely, to be a bug in your JavaScript as it is to be a bug in WebKit.
Avery
Comment 5 2010-02-23 05:02:20 PST
(In reply to comment #4) > The page loads several hundred kilobytes of JavaScript. It’s impossible for us > to determine whether this is a bug in WebKit or in your JavaScript without > spending a lot of time analyzing those hundreds of kilobytes of code. It’s as > likely, if not more likely, to be a bug in your JavaScript as it is to be a bug > in WebKit. I already spent some time distilling this bug to a single html file after combing through a lot of our own code; I'm not up to look through more code. You've got some choices: 1) Look at the YUI code yourself (its open source) and understand this problem better. Did you even try spending some time trying to debug this? Or did you just look at how many KB of JavaScript was being loaded? It's not clear from your comment whether you did anything at all. 2) Talk to someone from Yahoo to understand this better. 3) File this away as not-to-be-fixed; there is a workaround. The fact of the matter is that this works fine in Firefox; if this didn't work in Firefox then I would've just filed a bug against YUI. The folks at Yahoo could probably say the same thing in terms of pushing back to WebKit (i.e. it's not our fault). I'm just giving the WebKit team a heads up (I wasn't obligated to file this bug). Chances are, someone else will also encounter this bug since: 1) It's not a case that most people test for. 2) It's a case that's pretty common (e.g. I go to another website in the same window and then click the back button to come back to my web app). Pushing this bug back to me isn't helpful since I don't know what you did (besides looking at how much JS was coming down the pipe). This is really your responsibility to understand this bug better. Just saying "There's too much of your JS!" isn't helpful at all. Since it's not my JS. And who knows? It might not be Webkit's fault at all. In that case, I recommend doing (3).
Alexey Proskuryakov
Comment 6 2010-02-23 10:13:58 PST
Confirmed with r55087, as well as shipping Safari/WebKit 4.0.4. It is certainly not your responsibility to reduce bugs for us! I think Mark implied that without any known Web sites affected by this, the difficulty of dealing with a bug becomes a factor that may delay investigation. But even if no one starts working on this right away, it's important to track this problem, thanks a lot for reporting it! > I will also be filing a bug against YUI Please cross-reference the bug reports once you file it, so that we could share results of investigation. See also: bug 31413, bug 34851.
Avery
Comment 7 2010-02-23 17:17:52 PST
Note You need to log in before you can comment on or make changes to this bug.