Closed Bug 7954 (html4.01) Opened 25 years ago Closed 8 years ago

outstanding issues for full HTML 4.01 support

Categories

(Core Graveyard :: Tracking, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: ekrock, Assigned: ian)

References

(Depends on 6 open bugs, )

Details

(Keywords: helpwanted, html4, meta)

This is a meta bug for tracking purposes only. It "depends" on individual outstanding bugs with HTML 4.0 compliance and is a way to track them and to speed the documenting of any deviations, exceptions, or known bugs which remain at release. NOTE: This meta bug depends on individual HTML 4.0 compliance bugs, not the other way around! If you wish use this meta bug to track an individual HTML 4.0 bug, either make this bug depend on the individual bug, or in the individual bug, use this bug # in the "bugs which depend on this bug" field.
QA Contact: leger → beppe
QA Contact: beppe → ekrock
Depends on: 994
Depends on: metadata
Status: NEW → ASSIGNED
Depends on: 1994, longdesc
Depends on: 8979
Depends on: 2750
Depends on: 2800
Target Milestone: M15
Setting to M15 as this is a [META] bug for tracking only.
Depends on: 1882
Depends on: 4050
Depends on: 7230
Depends on: 678
Depends on: 14088
Depends on: 2055
Depends on: text-dir
Depends on: 3166
Depends on: 7304
Depends on: 6782
Depends on: 8938
Depends on: col-align-inherit
Depends on: 1802
Depends on: 8131
Depends on: 13015
Depends on: frame-longdesc
Depends on: 7559
Depends on: 19425
Depends on: 797
Depends on: 9140
Depends on: 21076
Depends on: 19312
Depends on: 18357
Depends on: 21638
Depends on: 14445
Depends on: 7515
Depends on: 22037
Depends on: 22153
Depends on: 2590
Depends on: 21456
Depends on: 11229
Depends on: 7112
Depends on: 1044
Target Milestone: M15 → M20
Setting to M20 as this is a [META] bug for tracking only.
Depends on: 24025
Depends on: 24125
Depends on: 24126
Depends on: 24815
Depends on: 15545
Keywords: meta
Depends on: 22820
Depends on: 26282
Depends on: 17962
No longer depends on: 26282
Depends on: 16157
No longer depends on: 24126
Depends on: 16157
No longer depends on: 24126
Depends on: 2068
No longer depends on: 24125
Depends on: 15799
No longer depends on: 24025
Depends on: 18644
No longer depends on: 22820
Depends on: 2970, 221
No longer depends on: 22153
Depends on: 1061, 2203
No longer depends on: 22037, 221
Depends on: 3326
No longer depends on: 2203
Marking helpwanted and (since this is just a META tracking bug) reassigning to nobody@mozilla.org so I don't get cc:d on every dependency change on every bug.
Assignee: ekrock → nobody
Status: ASSIGNED → NEW
Keywords: helpwanted
Changing QA contact to nobody@mozilla.org so I stop getting spammed.
QA Contact: ekrock → nobody
Depends on: Accesskey-XUL
No longer depends on: 21638
Depends on: 14362
No longer depends on: 21456
Depends on: basefont
No longer depends on: 21076
Depends on: 2634, 194
No longer depends on: 19425
Depends on: 7670, 1931
No longer depends on: 19312, 194
Depends on: 11431, 1864
No longer depends on: 18644, 1931
Depends on: 6306
No longer depends on: 1864
Depends on: 7834
No longer depends on: 18357
Depends on: Default-Quotes
No longer depends on: 17962
Depends on: 13354
No longer depends on: Default-Quotes
Depends on: 3248
No longer depends on: 16157
Summary: [META] outstanding HTML 4.0 compliance issues → [META] outstanding issues for full HTML 4.01 support
I'm the reporter for this bug, so I get email for every change on a dependent bug. I'd like to stop getting this significant volume of email. Is there any way a bug reporter can arrange to stop getting updates for a particular bug? If not, would it be possible for someone who actually wants to get these updates to create a replacement bug for this one with them as the reporter? Very sorry for the trouble. I'm simply reporting and cc:d on so many reports that I have to be careful to control flow in every way I can. Thanks for any assistance!
No there's no way to stop this, the RFE is at bug #17464.
Depends on: frameborder
No longer depends on: 15799
Depends on: 15799
No longer depends on: frameborder
*** Bug 53899 has been marked as a duplicate of this bug. ***
CC'ing self
adding some
Depends on: 16157
No longer depends on: Accesskey-XUL
Taking responsability for tracking this...
Assignee: nobody → ian
QA Contact: nobody → ian
Why is bug 2212 listed here? According to http://www.w3.org/TR/html401/struct/tables.html, user argents are not required to support the char= or charoff= attributes. Not to say that bug 2212 shouldn't be fixed, but it's not required for HTML 4.01 compliance.
This bug already contains many bugs that aren't required for HTML compliance. That's why it's called "full HTML compliance".
Depends on: 2749
No longer depends on: 16157
> This bug already contains many bugs that aren't required > for HTML compliance. > That's why it's called "full HTML compliance". Should this bug depend on bug #74073? I think so, ian@hixie.ch disagrees.
Depends on: 16157
No longer depends on: 1944
Depends on: 3687
No longer depends on: 16157
Added mozilla1.0 keyword since HTML 4.01 compliance is a design goal of mozilla.
Keywords: mozilla1.0
Depends on: 96579
Depends on: 96804
Depends on: 99063
Depends on: 102896
Depends on: 102906
Depends on: 102907
Depends on: 102915
Depends on: 103053
Depends on: 105693
Depends on: 53441
Depends on: 15499
Depends on: 96658
Depends on: 58197
Depends on: 107621
Mass removing self from CC list.
Now I feel sumb because I have to add back. Sorry for the spam.
Depends on: 105556
Blocks: 151993
No longer blocks: 151993
Depends on: 151993
Depends on: 153920
Depends on: 127798
No longer depends on: 46569
Depends on: 162993
Depends on: 96976
Depends on: 55623
Alias: html4.01
Keywords: mozilla1.0
Depends on: 164979
Depends on: 47522
Should bug 10512 be added? Then again the comments in 10512 indicate the mozilla team isn't intersted in full HTML 4.01 support.
Same story with the WONTFIXed basefont bug 3875.
Based on reading the bugs referenced by Comment #17 and Comment #18, where it is stated by Mozilla/Netscape that 100% HTML 4.01 support is not going to happen, I really don't see the purpose of this META tracking bug. It seems obsolete, or end-of-lined, and thus should be marked WONTFIX.
Depends on: 10512
just because it's not going to be 100%, doesn't mean it isn't worth tracking exactly which bits aren't compliant and whether they are going to be fixed or not.
Depends on: 70978
Depends on: 95549
No longer depends on: 53441
It seems that Mozilla isn't interested in HTML 4.01 support According to comments in bug #692032 Mozilla isn't an XHTML user agent either. In particular ``XHTML isn't part of the current, official Mozilla agenda''. So I'm curious to know what goals are Mozilla pursuing? ISO/IEC 15445 perhaps? Maybe Mozilla isn't actually an HTML user agent? I suppose this isn't the correct forum to be rasing these concerns.
Russel: We don't have #692032 bug, yet. Luckily. Which bug do you refer to?
Sorry, It's bug #69032. Apperently Mozilla isn't an HTML UA, it isn't an XHTML UA, it is supposed to be an XML (+DOM +CSS) UA. Well, the goals of Mozilla seems to vary from place to place, and from person to person.
Depends on: 196735
Depends on: bearded-imagemap
Depends on: 192077
Depends on: 147446
Depends on: 45375
Keywords: html4
Summary: [META] outstanding issues for full HTML 4.01 support → outstanding issues for full HTML 4.01 support
Summary: outstanding issues for full HTML 4.01 support → [META] outstanding issues for full HTML 4.01 support
Depends on: 44306
Depends on: 127137
Removing [META]. We have keywords for that.
Summary: [META] outstanding issues for full HTML 4.01 support → outstanding issues for full HTML 4.01 support
Should bug 3655 be on here?
bug 189643 ? (see bug 1882 for discussion on standards compliancy)
Depends on: 277738
No longer depends on: readonly
Depends on: 244312
No longer depends on: 244312
Five and a half years later an update. Shouldn't this bug be closed now that we have HTML5?
(In reply to comment #27) > Five and a half years later an update. Shouldn't this bug be closed now that we > have HTML5? No, HTML5 is just a superstructure over HTML4, so without that being properly implemented, we are missing in HTML5 arena as well.
That's incorrect. HTML5 did not take HTML4 into account and is not a superset.
Regardless, Firefox needs to support HTML 4 for quite some time if it wants to remain a browser to be taken seriously.
There are 70+ users following this bug who do not want to lsiten in on a debate about the true nature of HTML5 and HTML 4. The question was, do Mozilla need to have this bug open? I was trying to help closing no longer needed bugs. HTML 4 is supported BY supporting HTML 5. There is only one HTML parser in Firefox and there is only one DOM tree. Firefox has switched to an HTML5 compliant parser. So is this bug helpful to keep track of stuff to implement, or are there better ways?
This is a tracking bug and 22 bugs it tracks are still open. This more or less should end this unnecessary discussion.
blocking-b2g: 2.2r? → ---
This bug is no longer being used to track/prioritize engineering work, so I'm going to close it out.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.