Bug 7788
| Summary: | www.live.com: umbrella bug | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Alice Liu <alice.barraclough> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Major | CC: | a, aroben, ian, webkit |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 420+ | ||
| Hardware: | Mac | ||
| OS: | OS X 10.4 | ||
| URL: | http://www.live.com | ||
| Bug Depends on: | 8993, 9016, 9017, 9035, 9092, 9093, 9124, 9127, 9325 | ||
| Bug Blocks: | |||
Alice Liu
safari does not render much of the www.live.com page. this is likely to be caused by the same issues as 6519 but we are keeping separate bugs for the possibility that there are non-overlapping issues, and for the compatibility hit list.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alice Liu
<rdar://problem/4419198>
Geoffrey Garen
Interestingly, the sniffing on this page, as opposed to the other MS pages, is
navigator.userAgent.indexOf("Mozilla")>=0
which we pass.
Alexander Kellett
it uses the same HTMLDocument.prototype functionality as we are missing in the related bugs, so while it is being detected as mozilla, we don't support everything needed in any case. which means btw that without user agent spoofing we couldn't support this page /unless/ we implemented these mozilla related extensions, just the ie methods would not do.
Mark Malone
Like live, SAP uses HTMLDocument.prototype to add features to Firefox like innerHTML; which webkit supports! Browser sniffing is bad. Let's get these changed to object detection calls or we'll be chasing this forever.
Geoffrey Garen
HTMLDocument.prototype is fixed now.
Darin Adler
With all the blocking bugs marked resolved, what remains to be fixed at www.live.com? Does this still deserve a spot on our hit list?
Adam Roben (:aroben)
As far as I can tell, live.com is fully functional in the latest nightlies. I'd vote for removing this from the hitlist and closing this bug.
Robert Blaut
As Adam said above the site already works fine with Webkit/Safari so I resolve this bug as FIXED.
Feel free to reopen this bug if you find any issues.