This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27947 - Specify forceRedraw as a no-op
Summary: Specify forceRedraw as a no-op
Status: NEW
Alias: None
Product: SVG
Classification: Unclassified
Component: Backwards Compatibility (show other bugs)
Version: SVG 2.0
Hardware: PC All
: P2 normal
Target Milestone: Test Suite
Assignee: Doug Schepers
QA Contact: SVG Public List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-03 08:45 UTC by Simon Pieters
Modified: 2015-02-03 08:45 UTC (History)
0 users

See Also:

Attachments

Description Simon Pieters 2015-02-03 08:45:30 UTC 
suspendRedraw/unsuspendRedraw/unsuspendRedrawAll are specified as no-ops but not forceRedraw. In implementations they are all no-ops. Please specify forceRedraw as a no-op to match implementations.

There is non-zero Web content using these (https://groups.google.com/a/chromium.org/d/msg/blink-dev/bSmQh2GLt_4/R3FXnXrJ7b0J ), so dropping them would cause those pages to break for almost no benefit.

http://software.hixie.ch/utilities/js/live-dom-viewer/saved/3403

(Presto updates the rendering during script execusion not because of the call to forceRedraw but because Presto has an interuptable JS engine and generally updates rendering when script takes long to run.)