RFC 5147 plain text position fragments
Reported by hmdmhdfm...@gmail.com, Mar 22 2011
Chrome Version : 10.0.648.151 (Offizieller Build 78498) URLs (if applicable) : http://en.wikipedia.org/w/index.php?title=Robustness_principle&oldid=420101632#External_links Other browsers tested: IE9 RC (64bits) FAIL What steps will reproduce the problem? 1. Go to permalink http://en.wikipedia.org/w/index.php?title=Robustness_principle&oldid=420101632#External_links 2. Click on http://www.postel.org/ien/txt/ien111.txt#line=1483 What is the expected result? As per RFC 5147 line 1483 in IEN 111 What happens instead? The RFC 5147 fragment #line=1483 position is ignored Please provide any additional information below. IMO RFC 5147 makes sense, and supporting at least line= should be simple. There is a similar open issue wrt page= fragments in application/pdf, that's presumably harder.
Jun 30 2011,
Why does it take months to confirm this simple issue? Just open a random text file with your favourite text editor and go to a position within the file, e.g., line 100. Then open the file in Chrome with a file:// URI. Add #line=100 to the URI in the omnibox, click enter, and if Chrome does not show line 100 confirm this issue.
Jul 16 2011,
Jul 20 2011,
You need to file a bug report for WebKit as well.
Jul 20 2011,
And you should test Opera browser and file a bug with them if necessary.
Aug 10 2012,
Closing old bug as obsolete. Please file a new bug (with details) if this problem is still occurring for you.
Oct 13 2012,
This issue has been closed for some time. No one will pay attention to new comments. If you are seeing this bug or have new data, please click New Issue to start a new bug.
Mar 11 2013,
Sign in to add a comment