@PointedEars2 @mathias they are still required to be implemented by user agents however.
-
-
Replying to @annevk1 reply 0 retweets 0 likes
-
-
Replying to @PointedEars2
@PointedEars2@mathias implementers of new engines need these features to be competitive. Not defining them is bad for the web’s health.1 reply 0 retweets 0 likes -
Replying to @PointedEars2
@PointedEars2@annevk@mathias Making it easier for new implementors to become competitive is keeping the web in dark ages? O_o1 reply 0 retweets 1 like -
Replying to @PointedEars2
@PointedEars2@m_gol@annevk@mathias "obsolete, replaced" doesn't mean "not used by 90% of websites", sadly.1 reply 0 retweets 0 likes -
Replying to @really_bz
@bz_moz@m_gol@annevk@mathias It may justify support for a while. It does _not_ justify a *new* *requirement* for support by a “standard”.3 replies 0 retweets 0 likes
@PointedEars2 @m_gol @annevk @mathias If support is needed for compat, the standard needs to define what that support needs to behave as.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.