Closed
Bug 1287011
Opened 10 years ago
Closed 10 years ago
Remove preference gfx.filter.nearest.force-enabled
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
FIXED
mozilla50
| Tracking | Status | |
|---|---|---|
| firefox50 | --- | fixed |
People
(Reporter: dbaron, Assigned: dbaron)
Details
Attachments
(1 file)
|
4.28 KB,
patch
|
gw280
:
review+
|
Details | Diff | Splinter Review |
MozReview-Commit-ID: IFW2Ukwx4fH
| Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8771195 -
Flags: review?(gwright)
| Assignee | ||
Comment 2•10 years ago
|
||
Oops, forgot to refresh with the bulk of the commit message, which is:
This preference was added in bug 747274, and the need for it (i.e.,
having it default to a different value on Android) was removed a few
weeks later in bug 750598.
Whether we honor the preference depends on which drawing function we go
through, which bug 720531 will make even more inconsistent than it
already is (by causing it to be honored for border-image-repeat: space,
but not other values of border-image-repeat).
Rather than trying to clean it up, it seems best to remove it, since its
initial purpose appears to have been having a different default on
Android, which we longer need.
Updated•10 years ago
|
Attachment #8771195 -
Flags: review?(gwright) → review+
Pushed by dbaron@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/0bb4cf8a5759
Remove preference gfx.filter.nearest.force-enabled. r=gw280
Comment 4•10 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
status-firefox50:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla50
You need to log in
before you can comment on or make changes to this bug.
Description
•