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
Assuming we continue having numerical priorities (see #4591), should the highlight priority be an integer instead of a double?
Downside of integers: likely to be used like BASIC line numbers, counting in 10s (or in 100s) to make insertion between two layers easy. Workable, but clumsy.
Downside of doubles: depending on the internal precision used to store these, in some browsers two very close numbers could be considered equal, while in other browsers they would be different. Depending on the order of insertion into CSS.highlights, this could result in the opposite ordering, and therefore interop problems.
The text was updated successfully, but these errors were encountered:
@frivoal@hober@fantasai I don't have strong opinions on this, but I'm in favor of keeping this simple and just using integers. Are you all okay with that?
Given that there is the escape hatch of running through the HighlightRegistry and changing all of the numbers to whatever you like, I am also in favor of integers
Assuming we continue having numerical priorities (see #4591), should the highlight priority be an integer instead of a double?
Downside of integers: likely to be used like BASIC line numbers, counting in 10s (or in 100s) to make insertion between two layers easy. Workable, but clumsy.
Downside of doubles: depending on the internal precision used to store these, in some browsers two very close numbers could be considered equal, while in other browsers they would be different. Depending on the order of insertion into
CSS.highlights
, this could result in the opposite ordering, and therefore interop problems.The text was updated successfully, but these errors were encountered: