Personally, I'd consider Firefox's behavior a bug; the Firefox people
all but admit as much themselves in that article you linked (I
consider "works inconsistently" to be a euphemism for "bugged").
Given that Mochikit is all about overcoming weird little browser bugs
like this and hiding them behind functions that work consistently
across all browsers, it seems to me that "fixing" updateNodeAttribute
would be the proper course of action.
However:
A) I never use that function, so who am I to talk?
B) If someone could make the case that Firefox's behavior is a feature
and not a bug, I could then see leaving the function as is and simply
changing the documentation.
Just my two cents.
Jeremy
On May 13, 1:38 pm, "Per Cederberg" <
cederb...@...> wrote:
> I stumbled across an issue with "value" attributes in <input> nodes
> about a month ago. It seems the behavior is different when using
> node.value vs. node.setAttribute("value"..):
>
>
http://trac.mochikit.com/ticket/302>
> So the question now it whether or not to patch
> MochiKit.DOM.updateNodeAttribute(). Or if I should just update the
> docs with a short note and link to the relevant page at MDC:
>
>
http://developer.mozilla.org/en/docs/DOM:element.setAttribute (see the "Notes")
>
> Opinions?
>
> Cheers,
>
> /Per
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "MochiKit" group.
To post to this group, send email to
mochikit@...
To unsubscribe from this group, send email to
mochikit-unsubscribe@...
For more options, visit this group at
http://groups.google.com/group/mochikit?hl=en-~----------~----~----~----~------~----~------~--~---
