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
jcollins-g opened this issue
Feb 1, 2019
· 1 comment
Labels
P1A high priority bug; for example, a single project is unusable or has many test failurestype-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
Noticed a console warning while working on Javascript.
[Deprecation] Using unescaped '#' characters in a data URI body is deprecated and will be removed in M71, around December 2018. Please use '%23' instead. See https://www.chromestatus.com/features/5656049583390720 for more details.
The text was updated successfully, but these errors were encountered:
jcollins-g
added
P2
A bug or feature request we're likely to work on
type-code-health
Internal changes to our tools and workflows to make them cleaner, simpler, or more maintainable
labels
Feb 1, 2019
This issue becomes real in Chrome 72, manifesting as missing greater than symbols between components in the header.
jcollins-g
added
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
P1
A high priority bug; for example, a single project is unusable or has many test failures
and removed
type-code-health
Internal changes to our tools and workflows to make them cleaner, simpler, or more maintainable
P2
A bug or feature request we're likely to work on
labels
Feb 1, 2019
P1A high priority bug; for example, a single project is unusable or has many test failurestype-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
Noticed a console warning while working on Javascript.
[Deprecation] Using unescaped '#' characters in a data URI body is deprecated and will be removed in M71, around December 2018. Please use '%23' instead. See https://www.chromestatus.com/features/5656049583390720 for more details.
https://www.chromestatus.com/features/5656049583390720
The text was updated successfully, but these errors were encountered: