Open
Bug 1230437
Opened 9 years ago
Updated 2 years ago
additional tests to confirm unicode-range loading behavior
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox45 | --- | affected |
People
(Reporter: jtd, Unassigned)
References
Details
Follow up work from bug 1119062. dbaron thinks we should add more tests for unicode-range loading behavior (bug 1119062, comment 7): "One other thought, though (since you made me look at what the test coverage is): given that the reason for unicode-range to exist is that it allows a way of not bothering to download a font at all based on character ranges, it seems like it's probably worth adding a mochitest to actually test the "lack of download" aspect of it (with a base case that should be downloaded). It shouldn't be too hard to do in the manner of test_bug517224.html and bug517224.sjs in layout/style/test/ (although you probably want multiple tests, like the somewhat more complicated visited_image_loading test in the same directory)." So basically we need to run through a set of tests similar to the ones in test_unicode_range_loading.html that confirm from the server-side via sjs scripts that only certain font resources are pulled from the server. Seems like it might be possible to integrate the test into test_unicode_range_loading.html using promisified XHR requests to check the server state after each test.
Comment 1•2 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.
Assignee: jd.bugzilla → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•