Closed
Bug 1459948
Opened 7 years ago
Closed 2 years ago
Don't include super long data URIs in Highlights
Categories
(Firefox :: New Tab Page, defect, P3)
Firefox
New Tab Page
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox61 | --- | wontfix |
firefox62 | --- | fix-optional |
People
(Reporter: ntim, Unassigned)
References
Details
Attachments
(2 files)
STR:
- Have highlights disabled
- Visit a super long data URI
- Enable Highlights
- Open the new tab page
AR:
- Firefox freezes
- The super long data URI appears on the new tab page
ER:
- Highlights should be smart and ignore the super long URL for performance concerns
Reporter | ||
Comment 1•7 years ago
|
||
Here's the data URI (was too large to put in a comment).
Updated•7 years ago
|
Whiteboard: [fxperf]
Comment 2•7 years ago
|
||
Setting this as a P3 and fix-optional for this release unless there are strong objections. Thoughts :ntim
Comment 3•7 years ago
|
||
Another way to trigger this is to execute the following in the developer toolbar:
>> screenshot --fullpage
That pretty much makes the newtab page unusable for me until I clear my downloads.
Comment 4•7 years ago
|
||
Highlights after a screenshot from Developer Toolbar.
Comment 5•7 years ago
|
||
Not a common case, but when it happens, it apparently makes the new tab unusable. To fix it or could just not show data: URIs at all, or establish a length limit to crop
Whiteboard: [fxperf] → [fxperf:p2]
Comment 6•6 years ago
|
||
The UI issue in Comment 4 was fixed by Bug 1464349.
Updated•6 years ago
|
Whiteboard: [fxperf:p2] → [fxperf:p3]
Assignee | ||
Updated•5 years ago
|
Component: Activity Streams: Newtab → New Tab Page
Updated•2 years ago
|
Severity: normal → S3
Comment 7•2 years ago
|
||
I don't think this is relevant with the current about:newtab anymore. Please feel free to reopen if this still applies in some way that I have overlooked.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
Whiteboard: [fxperf:p3]
You need to log in
before you can comment on or make changes to this bug.
Description
•