Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Renaming the Gecko DOM Reference
4 views
Skip to first unread message
Janet Swisher
Oct 21, 2011, 8:23:00 PM10/21/11
to dev-mdc
Throwing this idea out for feedback:
Proposal: The "Gecko DOM Reference" should be renamed the "DOM Reference".
In the past, different browsers' DOM implementations varied much more
than they do now that things are more standardized. The DOM reference on
MDN should be a guide to the present and the future, not the past. While
it probably won't ever fully document other engines' implementation, the
MDN DOM reference can reasonably aspire to be a reference for what web
developers should write code for, across modern browsers, not just
Gecko. Compatibility tables can take care of documenting what
differences still exist. There is some Gecko-specific text, especially
in the prefatory sections, but this can be rewritten to take a
historical perspective.
Thoughts?
Proposal: The "Gecko DOM Reference" should be renamed the "DOM Reference".
In the past, different browsers' DOM implementations varied much more
than they do now that things are more standardized. The DOM reference on
MDN should be a guide to the present and the future, not the past. While
it probably won't ever fully document other engines' implementation, the
MDN DOM reference can reasonably aspire to be a reference for what web
developers should write code for, across modern browsers, not just
Gecko. Compatibility tables can take care of documenting what
differences still exist. There is some Gecko-specific text, especially
in the prefatory sections, but this can be rewritten to take a
historical perspective.
Thoughts?
Sheppy
Oct 22, 2011, 1:06:44 AM10/22/11
to
On Oct 21, 8:23 pm, Janet Swisher <jswis...@mozilla.com> wrote:
> Throwing this idea out for feedback:
>
> Proposal: The "Gecko DOM Reference" should be renamed the "DOM Reference".
Yes. This absolutely needs to be done.
> Throwing this idea out for feedback:
>
> Proposal: The "Gecko DOM Reference" should be renamed the "DOM Reference".
Eric Shepherd
Developer Documentation Lead
Mozilla
http://www.bitstampede.com/
Teoli
Oct 22, 2011, 5:30:42 AM10/22/11
to
On 22.10.11 02:23, Janet Swisher wrote:
> Throwing this idea out for feedback:
>
> Proposal: The "Gecko DOM Reference" should be renamed the "DOM Reference".
>
I absolutely agree. I almost renamed the page last Thursday, when I
> Throwing this idea out for feedback:
>
> Proposal: The "Gecko DOM Reference" should be renamed the "DOM Reference".
>
slightly revamped the DOM portal page, but as the agnosticism work on
all the referenced DOM pages is huge, I refrained.
But I think we should rename it as soon as possible.
Especially as work on DOM Level 4 has started and should lead to a
quite-portable DOM. (And Webkit has started adapting HTML DOM interfaces
to match the standard, like Gecko did for Fx 4, and continue to do so)
Sheppy
Oct 22, 2011, 2:06:15 PM10/22/11
to
On Oct 22, 5:30 am, Teoli <news.fakeaddr...@localhost.invalid> wrote:
> On 22.10.11 02:23, Janet Swisher wrote:> Throwing this idea out for feedback:
>
> > Proposal: The "Gecko DOM Reference" should be renamed the "DOM Reference".
>
> I absolutely agree. I almost renamed the page last Thursday, when I
> slightly revamped the DOM portal page, but as the agnosticism work on
> all the referenced DOM pages is huge, I refrained.
>
> But I think we should rename it as soon as possible.
I feel we should go ahead with the rename even though the
> On 22.10.11 02:23, Janet Swisher wrote:> Throwing this idea out for feedback:
>
> > Proposal: The "Gecko DOM Reference" should be renamed the "DOM Reference".
>
> I absolutely agree. I almost renamed the page last Thursday, when I
> slightly revamped the DOM portal page, but as the agnosticism work on
> all the referenced DOM pages is huge, I refrained.
>
> But I think we should rename it as soon as possible.
agnosticization (look, I invented a word) of the documentation isn't
finished. This will help, hopefully, remind people to make new content
browser-agnostic, but also remind us to keep working toward cleaning
up the existing material.
0 new messages