[Webkit-unassigned] [Bug 35286] Hitting back propagates button value to other buttons

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=35286





--- Comment #5 from Avery <misteravery+bugzilla at gmail.com>  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).

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.