Bug 9711
| Summary: | More Safari AJAX history bugs | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | ddkilzer |
| Priority: | P4 | ||
| Version: | 420+ | ||
| Hardware: | Mac | ||
| OS: | OS X 10.4 | ||
| URL: | http://bloomd.home.mchsi.com/histapi/howitworks.html | ||
Eric Seidel (no email)
Another site I ran accross on the net. Although it doesn't break down into a single test case, the essay he's written about how he got safari support working (through serious hacks) is useful, and probably could be broken up into bugs.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
David Kilzer (:ddkilzer)
I am 99% sure this was fixed with Anders' patch for Bug 6309 (and is thus a duplicate). The workaround is very interesting, though!
Have you tried a nightly WebKit build, Eric? :)
Anders Carlsson
That's right. With 6309 fixed, Safari can use the "regular" way of doing AJAX history
*** This bug has been marked as a duplicate of 6309 ***