Closed
Bug 407636
Opened 17 years ago
Closed 17 years ago
[meta] Track websites broken with NS_ERROR_DOM_WRONG_DOCUMENT_ERR
Categories
(Core Graveyard :: Tracking, defect)
Core Graveyard
Tracking
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: BijuMailList, Unassigned)
References
Details
(Keywords: meta)
Tracking all websites broken with NS_ERROR_DOM_WRONG_DOCUMENT_ERR so that we are not creating duplicate.
Updated•17 years ago
|
Keywords: meta
OS: Windows XP → All
Hardware: PC → All
Summary: Track websites broken with NS_ERROR_DOM_WRONG_DOCUMENT_ERR → [meta] Track websites broken with NS_ERROR_DOM_WRONG_DOCUMENT_ERR
Comment 1•17 years ago
|
||
Mike, see bug 47903, comment 87, some of the dependancies on this bug should probably be fixed before Firefox 3 comes out, but tech evangelism bugs can't be made blocking1.9+.
Flags: blocking1.9?
Comment 2•17 years ago
|
||
Still, we never mark meta bugs as blocking anything, as there's really nothing to do in the bug itself.
Comment 3•17 years ago
|
||
Fwiw, I don't agree with that. What is being done in this bug is tracking tech evangelism bugs that possibly should block the Firefox 3 release because of the NS_ERROR_DOM_WRONG_DOCUMENT_ERR error being thrown.
But I guess the way to go instead is the ability to mark tech evangelism bugs as blocking a release then?
This is just a tracker bug, no action is needed in this bug. We have other bugs on the actual issue. So marking this blocking-
Flags: blocking1.9? → blocking1.9-
Comment 5•17 years ago
|
||
Those other bugs can't be marked blocking1.9+.
Comment 6•17 years ago
|
||
(In reply to comment #5)
> Those other bugs can't be marked blocking1.9+.
If they are real problems, they do not need to be in Tech Evangelism. Move the bugs to a component where developers actually do work.
Comment 7•17 years ago
|
||
You make it sound like tech evangelism bugs aren't real problems. I think they are real problems, especially when something has changed on trunk that made functionality on websites stop working.
I think in that case, Mozilla has a responsibility that at least top sites like Yahoo and Google stay working.
I just want to be sure certain tech evangelism issues are fixed before Firefox 3 comes out. I guess it's likely that Google and Yahoo fix their sites, but still.
In any case, if this bug can't be blocking1.9+, then I don't really see the need for this bug, because dependencies are already set on bug 47903.
I guess if we want to mark blocking+ on evangelism bugs for certain sites you should nominate the bugs for the individual sites, as I think this bug is a tracker for all of them.
As for the technical issue of if we should be throwing this exception or not, that discussion and work should happen elsewhere, and thus any blocking nomination for that decision should be elsewhere.
Comment 9•17 years ago
|
||
(In reply to comment #8)
> I guess if we want to mark blocking+ on evangelism bugs for certain sites you
> should nominate the bugs for the individual sites, as I think this bug is a
> tracker for all of them.
Like I said, that's not possible.
In any case, I've filed bug 407970 to make it possible for tech evangelism bugs to block a release.
> As for the technical issue of if we should be throwing this exception or not,
> that discussion and work should happen elsewhere, and thus any blocking
> nomination for that decision should be elsewhere.
I don't question how trunk currently behaves. I think it's fine.
I guess I'm not making myself very clear :/
Comment 10•17 years ago
|
||
Google Android submission page is affected:
http://code.google.com/android/adc-submit/
I posted a message to http://groups.google.com/group/android-challenge/browse_frm/thread/20a656416688a540
Started a thread in mozilla.dev.planning about if we should stop throwing:
http://groups.google.com/group/mozilla.dev.platform/browse_thread/thread/efbb0861ca5d0e67
Comment 12•17 years ago
|
||
The largest (and in practice almost the only) Swedish ticket booking site for train tickets works in FF2 but doesn't work in FF3. Someone suggested that this ticket site was broken by the same check-in that is being discussed here.
So, maybe this bug (see link below) should be added to the list of broken sites?
https://bugzilla.mozilla.org/show_bug.cgi?id=417076
Comment 13•17 years ago
|
||
jst just filed bug 418755, "Stop throwing WRONG_DOCUMENT_ERR since the web can't deal".
Comment 14•17 years ago
|
||
Should these bugs be closed now that bug 418755 has landed?
Reporter | ||
Comment 15•17 years ago
|
||
all dependents got fixed after bug 418755 has landed.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Comment 16•17 years ago
|
||
(In reply to comment #15)
> all dependents got fixed after bug 418755 has landed.
That doesn't mean the problem isn't still there on each of these sites. It's been my understanding all along that what each of these sites is doing is still wrong; it just turns out that doing things the wrong way is such a widespread practise that we can't yet throw this error.
The sites in question should still be evangelised to fix their code, however, so I'm reopening this bug.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I don't think we keep evangelism bugs for making sites comply with w3c specs, but rather to make them work with firefox.
That doesn't mean that you (or anyone else) can't contact the site still.
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•