[Webkit-unassigned] [Bug 27444] Wrong FrameLoader::activeDocumentLoader when loading an invalid URL.

[bugzilla-daemon at webkit.org]

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


Brady Eidson <beidson at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #33081|review?                     |review-
               Flag|                            |




--- Comment #2 from Brady Eidson <beidson at apple.com>  2009-07-20 13:37:50 PDT ---
(From update of attachment 33081)
Thanks for your interest and thanks for you patch, but I think you're chasing
down a non-issue.

Most importantly, a Frame shouldn't ever consider a failed, non-committed load
as it's current DocumentLoader.  Making this change would be a change in
behavior that many WebKit applications do not expect. Most notably, Safari
would break with this change.

Can you explain an example of an application you're working on where this
change is desirable?  And why?

Also, if a layout test times out with your patch in but runs correctly without
your patch, that *is* indicative of a regression with your patch.  I bet the
test is catching exactly the WebKit API breakage that I alluded to.

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