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
Arguably marky shouldn't clear all the entries in marky.clear(), only its own. But this would require changing the current mark/measure system to prefix all marks, as suggested here: w3c/resource-timing#89 (comment)
Thus far I've assumed with marky that overall usage of the User Timing API is low enough that there is little danger of collisions; in fact my goal was to increase visibility of the UT API and get people to start using it. :) But as more libraries like React and Vue start to use it themselves, it may make sense to namespace. Arguably it would become a breaking change though.
The text was updated successfully, but these errors were encountered:
Arguably marky shouldn't clear all the entries in
marky.clear()
, only its own. But this would require changing the current mark/measure system to prefix all marks, as suggested here: w3c/resource-timing#89 (comment)Thus far I've assumed with
marky
that overall usage of the User Timing API is low enough that there is little danger of collisions; in fact my goal was to increase visibility of the UT API and get people to start using it. :) But as more libraries like React and Vue start to use it themselves, it may make sense to namespace. Arguably it would become a breaking change though.The text was updated successfully, but these errors were encountered: