W3C home > Mailing lists > Public > www-svg@w3.org > February 2015

[Bug 27947] New: Specify forceRedraw as a no-op

From: <bugzilla@jessica.w3.org>
Date: Tue, 03 Feb 2015 08:45:30 +0000
To: www-svg@w3.org
Message-ID: <bug-27947-2017@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27947

            Bug ID: 27947
           Summary: Specify forceRedraw as a no-op
           Product: SVG
           Version: SVG 2.0
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Backwards Compatibility
          Assignee: schepers@w3.org
          Reporter: simonp@opera.com
        QA Contact: www-svg@w3.org

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.)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 3 February 2015 08:45:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:39 UTC