34822 - Extensions need to be documented and examined

Status: RESOLVED WORKSFORME

(Documentation Graveyard :: Web Developer, defect, P3)

Description

[Hixie (not reading bugmail)]

Mozilla has implemented several extensions to CSS (e.g. -moz-border-radius), 
HTML (e.g. <blink>), HTTP (e.g. maybe -Moz-Layout-Mode), and so on.

We need to document these.

I guess the first step is to list all the extensions... Maybe a new bug needs to
be broken out for each relevant component and assigned to that module's owner,
with this bug as the parent dependency?

Comment 1

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

There's some info in:
http://lists.w3.org/Archives/Public/www-style/2000Apr/0033.html
bug 3935

Comment 2

[ekrock's old account (dead)]

Steve, is there any chance that the doc group could create a "mozilla extensions 
to CSS" document? Or facilitate the open source creation of one?

Comment 3

[rudman]

Accepting bug for now, changing product to Documentation.

Can't wait to document "blink"!

We'll solicit help from the mozilla doc community, and I'll reassign as 
appropriate.

Comment 4

[Hixie (not reading bugmail)]

Moving to "Web Developer" component, since this documentation is for people who
write websites more than for those who write Mozilla itself...

   <blink> - HTML extension
      Introduced in: An earlier version of Netscape Navigator
      Standard Compliant Equivalent: <span style="text-decoration: blink">
      Syntax: <blink> </blink>
      Description: An inline level element with blinking content.

Comment 5

[Asa Dotzler [:asa]]

Sorry for the spam.  New QA Contact for Browser General.  Thanks for your help
Joseph (good luck with the new job) and welcome aboard Doron Rosenberg

Comment 6

[Daniel Wang]

-> nobody

Comment 7

[Gordon P. Hemsley [:GPHemsley]]

Between MDN and various specs that have arisen since 2000, I'd say this is WFM.