Closed Bug 1388910 Opened 9 years ago Closed 1 year ago

remove support for '-moz-user-modify' CSS property

Categories

(Core :: CSS Parsing and Computation, task, P3)

task

Tracking

()

RESOLVED FIXED
134 Branch
Tracking Status
firefox57 --- wontfix
firefox134 --- fixed

People

(Reporter: dbaron, Assigned: emilio)

References

(Blocks 1 open bug)

Details

(Keywords: dev-doc-needed, perf-alert, site-compat)

Attachments

(1 file)

Based on https://lists.w3.org/Archives/Public/www-style/2015Apr/0406.html I think we should consider removing support for the -moz-user-modify CSS property. The original spec for this was: https://www.w3.org/TR/2000/WD-css3-userint-20000216#user-modify It seems like the only thing we do with the property is, under some conditions, change whether the caret is visible: https://searchfox.org/mozilla-central/rev/c329d562fb6c6218bdb79290faaf015467ef89e2/layout/base/nsCaret.cpp#549 This doesn't particularly seem to match the intent of the property, and makes it seem like we should probably remove the caret-related behavior since it doesn't seem to do anything else. If we remove it, we might need something else to control the caret behavior, though, since the property does appear to be used to control caret visibility in our UA style sheets. Alternatively, we could change the property to be accessible only from UA style sheets, and stop exposing it to the Web.
Priority: -- → P3
Keywords: site-compat
Type: enhancement → task
Blocks: 1788820
Severity: normal → S3
Depends on: 1920118
No longer blocks: 1788820
Assignee: nobody → emilio
Status: NEW → ASSIGNED
Pushed by ealvarez@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/130794a57298 Remove -moz-user-modify property. r=dshin

Pushed by mkmelin@iki.fi:
https://hg.mozilla.org/comm-central/rev/f260cbb2bd1c
no longer package bin/res/designmode.css for Thunderbird. rs=bustage-fix

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 134 Branch

This lead to a 2.8% improvement on Sp3-editor-tiptap/Highlight/Sync/opt fission.

Edit:
This is effectively bringing the regression from bug 1934501 back to baseline. (Focus on this perfherder graph.
Baseline: 32ms
Post-regression from bug 1934501 : ~34ms
Post improvement from this bug: 32ms

(In reply to Pulsebot from comment #2)

Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/130794a57298
Remove -moz-user-modify property. r=dshin

Perfherder has detected a browsertime performance change from push 130794a57298f50adb259e805866e563ec72cf63.

Improvement:

Ratio Test Platform Options Absolute values (old vs new) Performance Profiles
6% speedometer3 Editor-TipTap/Highlight/Sync windows11-64-shippable-qr fission webrender 33.52 -> 35.45 Before/After

This was initially opened as a regression alert, but is actually an improvement as Mayank pointed out in the previous comment.

Keywords: perf-alert
Regressions: 1941134
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: