[Webkit-unassigned] [Bug 122589] Graphics backend without hardware accelerated compositing, and compositing disabled by Setting, causes CSS3 Transform not correct

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=122589





--- Comment #3 from Chen Zhixiang <chenzx at cn.fujitsu.com>  2013-10-09 23:39:30 PST ---
Disabling compositing method:

void RenderLayerCompositor::cacheAcceleratedCompositingFlags() 
{ 
    bool hasAcceleratedCompositing = false; 
    bool showDebugBorders = false; 
    bool showRepaintCounter = false; 
    bool forceCompositingMode = false; 

    if (Settings* settings = m_renderView->document()->settings()) { 
〉 hasAcceleratedCompositing = false; //settings->acceleratedCompositingEnabled(); 

        // We allow the chrome to override the settings, in case the page is rendered 
        // on a chrome that doesn't allow accelerated compositing. 
        if (hasAcceleratedCompositing) { 
            Frame* frame = m_renderView->frameView()->frame(); 
            Page* page = frame ? frame->page() : 0; 
            if (page) { 
                ChromeClient* chromeClient = page->chrome()->client(); 
                m_compositingTriggers = chromeClient->allowedCompositingTriggers(); 
                hasAcceleratedCompositing = m_compositingTriggers; 
            } 
        } 

After applying the change to Qt-4.8 Windows GDI port, the result becomes wrong!

I have to say, the CSS3 transform should be right, no matter whether or not settings->acceleratedCompositingEnabled() is true/false.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.