Closed Bug 413891 Opened 17 years ago Closed 16 years ago

RSS discovery doesn't handle the general XML types case well

Categories

(Firefox Graveyard :: RSS Discovery and Preview, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WONTFIX
Firefox 3 beta4

People

(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)

References

()

Details

(Keywords: testcase)

Attachments

(1 file, 1 obsolete file)

Attached file Test case
This is a major inconsistency which I found out while testing a page which my friend sent me.  I'm attached a simplified test case.

We should be able to detect both feeds on this page.

The solution is a simple modification to the regular expression.  A patch is under way.
Flags: in-testsuite?
Attached patch Patch (v1) (obsolete) — Splinter Review
The patch includes an automated test to make sure this won't happen again.

Asking mano for review on the utilityOverlay.js related change.
Asking sayrer for review on the automated test.
Attachment #299007 - Flags: review?(sayrer)
Attachment #299007 - Flags: review?(mano)
sayrer: Note that the test is based on that of bug 377611, with the <link> elements changed to test for this bug.
Because I know sayrer will be asking this question, "no, IE7 doesn't discover either one of those feeds." And even though he won't be asking this question, "no, Opera 9.25 doesn't discover either one of those two feeds." So doing this will encourage people to use autodiscovery links that only work with Safari and Fx3+, but not Fx2 or Fx1.5 or IE7 or any Opera.

The current really slimy regex was designed to do exactly two things: give RDF fanatics who were so proud of having their own mimetype that they just had to use it in autodiscovery a way out, a need which is now met by "alternate feed", and to catch the default link to WordPress' RSS 0.92 feed, so we wouldn't have to bother sucking down their whole RSS 2.0 feed just to get titles and links, a need which no longer exists since the default WP templates now only link to the RSS 2.0 feed.

Before b1, I would have applauded dropping sniffing for title characters entirely; now, I think being even more incompatible with other browsers than we're already being while adding obscure false positives from 平rss仮 or érss doesn't sound like a good idea.
Comment on attachment 299007 [details] [diff] [review]
Patch (v1)

Robert is the right reviewer for this change.
Attachment #299007 - Flags: review?(mano)
Target Milestone: Firefox 3 beta3 → Firefox 3 beta4
sayrer: ping.
sayrer: re-ping :-)
Whiteboard: [has patch] [needs review sayrer]
IE8b1? Doesn't discover either one.
Hmm, should this be resolved as INVALID, or does my patch still apply here?
I'd vote for wontfix.
-> WONTFIX.  If you feel this needs to be fixed for some reason and considering what comment 3 suggests, please re-open.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Flags: in-testsuite?
Resolution: --- → WONTFIX
Whiteboard: [has patch] [needs review sayrer]
Attachment #299007 - Attachment is obsolete: true
Attachment #299007 - Flags: review?(sayrer)
Verified Wontfix.
Status: RESOLVED → VERIFIED
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: