My experience with the page visiblity spec process makes me not want to interact with that WG in the future. Huge waste of time.
@davidbaron http://lists.w3.org/Archives/Public/public-web-perf/2013Aug/0084.html … after forcing the broken behavior to REC first; see http://lists.w3.org/Archives/Public/public-web-perf/2011Oct/0033.html … and http://lists.w3.org/Archives/Public/public-web-perf/2011Sep/0037.html … etc
-
-
@davidbaron And repeatedly ignoring objections to the broken behavior, of course. And now that we forced interop on it, time to change it!Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@davidbaron https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/PageVisibility2/Overview.html … (not to be confused with "Page Visibility, Second Edition") tracking this change, fwiw.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bz_moz That dfn puzzled me when I saw it; change could be a big deal (positive, I *think*) for ad networks. Think it'll break sites? -
@davidbaron Mostly angry about being jerked about. We used do the right thing here; should have ignored the broken spec. Next time I will.
End of conversation
New conversation -
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.