Open Bug 1882999 Opened 2 years ago Updated 1 year ago

SecurityPolicyViolationEvent IDL uses USVString

Categories

(Core :: DOM: Security, task, P3)

Product:
Core
Component:
DOM: Security
Type:
task

Tracking

()

People

(Reporter: tschuster, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

(Whiteboard: [domsecurity-backlog])

Bug 1712690 updated the WebIDL for SecurityPolicyViolationEvent to be closer to the spec, but we are still not using USVString.

Technically wrong but doesn't really seem to be hurting anything so I'll throw it in the backlog. [I don't know why we have a mix of DOMString and UVString in the same API. Pick one and stick with it—don't make people memorize which properties can or can't have an unpaired surrogate! How often is that distinction going to matter?]

Severity: -- → S4
Priority: -- → P3
Whiteboard: [domsecurity-backlog]

Makes sense to look into which bits make sense as UTF8Strings when doing this.

You need to log in before you can comment on or make changes to this bug.