-
Notifications
You must be signed in to change notification settings - Fork 707
[css-highlight-api] negative priorities #4593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This was referenced Dec 13, 2019
If we go with numbers at all for this, I think we should allow negative numbers. A library author may want to say "my feature is cool, but if anything else is using the highlight api on this page, they should win over me." |
yes, let's allow them. |
Left the priority attribute as (implicitly) 'signed'. Closing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Assuming we continue having numerical priorities (see #4591):
If priorities are stored as integers (see [css-highlight-api] should priority be a floating point number or an integer? #4592), should we allow negative ones?
If negative integers or doubles are used, does a negative priority mean placement below the built-in highlights in the stacking order, and a positive number above them?
The text was updated successfully, but these errors were encountered: