Bug 15027 - Feed sniffing after XSLT processing.
Summary: Feed sniffing after XSLT processing.
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 523.x (Safari 3)
Hardware: PC OS X 10.4
: P2 Enhancement
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2007-08-20 15:01 PDT by Josh Peters
Modified: 2007-08-21 11:10 PDT (History)
1 user (show)

See Also:

Attachments
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 Josh Peters 2007-08-20 15:01:55 PDT 
This request concerns feed content sniffing.  I'm not going to suggest that content sniffing be turned off willy-nilly, but I hope to make a short case for changing the priority of sniffing, as I know that content sniffing can be a sore spot for lots of people interested in the web.

Given an XML-based language Webkit allows XML processing directives to be executed on the contents of a page.  For instance, one may create a custom markup language and specify an XML stylesheet to translate it into HTML.  Webkit currently breaks this benefit for web feeds (ie Atom or RSS).

Webkit needs to sniff the results of a XSLT to determine if the content is a feed or not.  If I have a page served as application/xml that consists of an Atom feed + XSLT translating that feed into an HTML page Webkit incorrectly interprets this as a web feed, not a HTML page.
Comment 1 Alexey Proskuryakov 2007-08-21 01:06:47 PDT 
Content sniffing is not in open source WebKit, so this report needs to be moved to Radar for Apple engineers to work on it.
Comment 2 Mark Rowe (bdash) 2007-08-21 09:06:47 PDT 
<rdar://problem/5425527>
Comment 3 Mark Rowe (bdash) 2007-08-21 09:07:54 PDT 
Moved to Radar.  Closing as INVALID due to this issue being outside of the scope of WebKit.
Comment 4 Josh Peters 2007-08-21 11:10:38 PDT 
Ah, well, thanks for the prompt inspection :)