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)
Core Graveyard
Tracking
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.
Reporter | ||
Updated•25 years ago
|
QA Contact: beppe → ekrock
Reporter | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•25 years ago
|
Assignee | ||
Updated•25 years ago
|
Depends on: character-alignment
Reporter | ||
Updated•25 years ago
|
Target Milestone: M15
Reporter | ||
Comment 1•25 years ago
|
||
Setting to M15 as this is a [META] bug for tracking only.
Assignee | ||
Updated•25 years ago
|
Depends on: col-align-inherit
Assignee | ||
Updated•25 years ago
|
Depends on: frame-longdesc
Assignee | ||
Updated•25 years ago
|
Reporter | ||
Updated•25 years ago
|
Target Milestone: M15 → M20
Reporter | ||
Comment 2•25 years ago
|
||
Setting to M20 as this is a [META] bug for tracking only.
Assignee | ||
Updated•25 years ago
|
Assignee | ||
Updated•25 years ago
|
Assignee | ||
Updated•25 years ago
|
Assignee | ||
Updated•25 years ago
|
Assignee | ||
Updated•25 years ago
|
Assignee | ||
Updated•25 years ago
|
Updated•25 years ago
|
Assignee | ||
Updated•25 years ago
|
Assignee | ||
Updated•25 years ago
|
Reporter | ||
Comment 3•25 years ago
|
||
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.
Reporter | ||
Comment 4•25 years ago
|
||
Changing QA contact to nobody@mozilla.org so I stop getting spammed.
QA Contact: ekrock → nobody
Updated•25 years ago
|
Assignee | ||
Updated•24 years ago
|
Assignee | ||
Updated•24 years ago
|
Assignee | ||
Updated•24 years ago
|
Assignee | ||
Updated•24 years ago
|
Assignee | ||
Updated•24 years ago
|
Assignee | ||
Updated•24 years ago
|
Assignee | ||
Updated•24 years ago
|
Assignee | ||
Updated•24 years ago
|
Assignee | ||
Updated•24 years ago
|
Assignee | ||
Updated•24 years ago
|
Assignee | ||
Updated•24 years ago
|
Summary: [META] outstanding HTML 4.0 compliance issues → [META] outstanding issues for full HTML 4.01 support
Reporter | ||
Comment 5•24 years ago
|
||
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!
Comment 6•24 years ago
|
||
No there's no way to stop this, the RFE is at bug #17464.
Comment 8•24 years ago
|
||
CC'ing self
Comment 9•24 years ago
|
||
adding some
Updated•24 years ago
|
Assignee | ||
Comment 10•24 years ago
|
||
Taking responsability for tracking this...
Assignee: nobody → ian
QA Contact: nobody → ian
Comment 11•24 years ago
|
||
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.
Comment 12•24 years ago
|
||
This bug already contains many bugs that aren't required for HTML compliance.
That's why it's called "full HTML compliance".
Assignee | ||
Updated•24 years ago
|
Comment 13•24 years ago
|
||
> 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.
Assignee | ||
Updated•24 years ago
|
Updated•23 years ago
|
Comment 14•23 years ago
|
||
Added mozilla1.0 keyword since HTML 4.01 compliance is a design goal of mozilla.
Keywords: mozilla1.0
Depends on: 94269
Depends on: 106065
Depends on: 109806
Comment 15•22 years ago
|
||
Mass removing self from CC list.
Comment 16•22 years ago
|
||
Now I feel sumb because I have to add back. Sorry for the spam.
Updated•22 years ago
|
Updated•22 years ago
|
Alias: html4.01
Keywords: mozilla1.0
Comment 17•22 years ago
|
||
Should bug 10512 be added?
Then again the comments in 10512 indicate the mozilla team isn't intersted in
full HTML 4.01 support.
Comment 18•22 years ago
|
||
Same story with the WONTFIXed basefont bug 3875.
Comment 19•22 years ago
|
||
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.
Comment 20•22 years ago
|
||
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.
Comment 21•22 years ago
|
||
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.
No longer depends on: 47979
Comment 22•22 years ago
|
||
Russel: We don't have #692032 bug, yet. Luckily.
Which bug do you refer to?
Comment 23•22 years ago
|
||
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.
Updated•21 years ago
|
Depends on: bearded-imagemap
Updated•21 years ago
|
Depends on: fieldset-eats-spaces
Updated•21 years ago
|
Keywords: html4
Summary: [META] outstanding issues for full HTML 4.01 support → outstanding issues for full HTML 4.01 support
Updated•21 years ago
|
Summary: outstanding issues for full HTML 4.01 support → [META] outstanding issues for full HTML 4.01 support
Comment 24•20 years ago
|
||
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
Comment 25•20 years ago
|
||
Should bug 3655 be on here?
Comment 26•20 years ago
|
||
bug 189643 ? (see bug 1882 for discussion on standards compliancy)
Comment 27•14 years ago
|
||
Five and a half years later an update. Shouldn't this bug be closed now that we have HTML5?
Comment 28•14 years ago
|
||
(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.
Assignee | ||
Comment 29•14 years ago
|
||
That's incorrect. HTML5 did not take HTML4 into account and is not a superset.
Comment 30•14 years ago
|
||
Regardless, Firefox needs to support HTML 4 for quite some time if it wants to remain a browser to be taken seriously.
Comment 31•14 years ago
|
||
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?
Comment 32•14 years ago
|
||
This is a tracking bug and 22 bugs it tracks are still open. This more or less should end this unnecessary discussion.
Updated•9 years ago
|
blocking-b2g: 2.2r? → ---
tracking-b2g:
backlog → ---
Comment 34•8 years ago
|
||
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
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
•