You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the desired behavior is that it's unspecified, because in practice implementations do not have a consistent order, and I recall past discussions were that some of them aren't willing to change. This should be specified explicitly, because it could be argued that the order should obviously match the DOM order unless specified otherwise. Alternatively, if implementations are willing to converge, we could specify that they match some specified order (e.g., DOM order).
The text was updated successfully, but these errors were encountered:
This was discussed in WICG/webcomponents#474. #1012 causes the order to become specified, as we concluded there; Gecko will not be able to comply, but they are currently non-compliant in other ways related to attribute order.
I think the desired behavior is that it's unspecified, because in practice implementations do not have a consistent order, and I recall past discussions were that some of them aren't willing to change. This should be specified explicitly, because it could be argued that the order should obviously match the DOM order unless specified otherwise. Alternatively, if implementations are willing to converge, we could specify that they match some specified order (e.g., DOM order).
The text was updated successfully, but these errors were encountered: