Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 422068

Summary: [Client] Use CSS3 rendering as fallback if neither CSS3, SVG or VML are detected
Product: [RT] RAP Reporter: Tim Buschtoens <tbuschto>
Component: RWTAssignee: Project Inbox <rap-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P2    
Version: 2.2   
Target Milestone: 2.2 RC1   
Hardware: All   
OS: All   
Whiteboard:

Description Tim Buschtoens CLA 2013-11-19 10:23:34 EST 
Trying to use SVG or VML (i.e. the GraphicsMixin) to render backgrounds in RAP may crash the browser, while using CSS3 properties that do not exists usually does not. Currently SVG/VML are the fallback for CSS3, but if those are not supported neither, CSS3 should still be attempted.
Comment 1 Ivan Furnadjiev CLA 2013-11-21 12:10:40 EST 
ProgressBar requires SVG/VML ( GraphicsUtil ). It will crash with "unknown" browser where both supportsSvg and supportsVml return false.
Comment 2 Ivan Furnadjiev CLA 2013-11-21 14:54:30 EST 
Proper solution will be to detect browsers supported technologies/standards (VML/SVG/CSS3) by querying some of their specific properties/functionalities instead of browser engine/version. Something like this:
http://stackoverflow.com/questions/654112/how-do-you-detect-support-for-vml-or-svg-in-a-browser
Comment 3 Ivan Furnadjiev CLA 2013-11-22 09:46:18 EST 
Improve SVG support detection. Use CSS3 as a fallback if GraphicsUtil is not supported (both supportsVml and supportsSvg return false). There is still a chance for application crash in pages with ProgressBar if SVG is not supported by the browser. To fix this a complete new implementation of ProgressBar is needed (not based on SVG).
Fixed in master with commit 420e2b7f9bc3fc75a7764cf392ace259af16bc86.