Bug 35399 - [Chromium] Chromium doesn't preserve hash fragments on about:blank URLs
Summary: [Chromium] Chromium doesn't preserve hash fragments on about:blank URLs
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore JavaScript (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Dirk Pranke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-25 12:14 PST by Dirk Pranke
Modified: 2010-03-25 10:42 PDT (History)
3 users (show)

See Also:

Attachments
Patch (2.18 KB, patch)
2010-02-25 12:26 PST, Dirk Pranke 		eric: review+
eric: commit-queue-
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Pranke 2010-02-25 12:14:52 PST 
See the discussion in http://bugs.webkit.org/show_bug.cgi?id=35180 for a bit of background.
Comment 1 Dirk Pranke 2010-02-25 12:26:41 PST 
Created attachment 49518 [details]
Patch
Comment 2 Dirk Pranke 2010-02-25 12:29:19 PST 
The bug tests whether or not setting a hash fragment on an "about:blank" URL is preserved. There has been some dispute in the past over whether or not we think it should be but current interpretation of <a href="http://www.ietf.org/rfc/rfc3986.txt">RFC 3986</a> is that hash fragments should be honored for all URL types by the browser (even though their interpretation is type-specific).

Note that Chromium and FF currently do not preserve this, but WebKit does.
Comment 3 Eric Seidel (no email) 2010-02-25 15:59:27 PST 
Comment on attachment 49518 [details]
Patch

OK.

Instead of mentioning the current behavior of Safari and Chrome in your test, I would simply state what the test does.  Since eventually all browsers will pass that test.

You used 2-space indent in your JS.

Fix those nits and land away! :)
Comment 4 Dirk Pranke 2010-02-25 16:56:04 PST 
patch landed as r55265. closing bug.