A method and system for checking and debugging browser compatibility issues
Permalink
Bookmark
Share
Twitter
Digg
Reddit
Facebook
Stumbleupon
Del.icio.us| IP.com Number | IPCOM000190123D |
|
|
|---|---|---|---|
| Dated | Nov 18, 2009 UTC | ||
| Size | 4 page(s) (112.1 KB) | ||
| Disclosed by |
|
||
Publication Summary
The article discribes a new mechanism which provides a communication channel to make multiple debugger are connected for debugging information exchanging, provides a hook handling mechanism for communicating the debugging in different browsers at runtime, and provides event simulation from one browser to another which enables user to just live in one browser but debug in different browsers| Country | |
|---|---|
| Language | English (United States) |
About this Publication
This document was submitted to IP.com's Prior Art Database and this preview is designed to provide you with information regarding the contents of this document by displaying up to the first four pages of the document as scaled page renderings and displaying a limited amount of text which was extracted from the document on the Text Preview Tab.
To find out more on how to obtain the entire document, click the Download tab. There is a charge for downloading some Prior Art Database documents; please examine carefully whether you believe this document fills your needs before purchasing.
For more information about the Prior Art Database, visit the Learn section of this website. Thank you for visiting IP.com's Prior Art Database! You may wish to check out our Global Patent Search website before you leave.
A method and system for checking and debugging browser compatibility issues
Display difference in such popular browsers as IE and Firefox, usually is due to the following factors, browser versions and configurations, computer types, screen size, front size, HTML errors, browser bugs and especially client-side script interpretation.The same JavaScript(JS) code is interpreted by different interpreters in different browser with unequal capabilities and features, which may result different display even errors.
To deal with these headache problems, Web page developers either avoid using advanced JS technique, or spend plenty of effort to debug in different browser runtime using different tools.The current browser compatibility test toolkits generally employ simulation or validation technique to report the unsupported HTML tags or JS grammars, without runtime report for JS code execution
The in-market browser compatibility test tools can be categorized as followings
1) Validation: checks the markup validity of web documents in HTML, XHTML. E.g. Validator.W3.org, BrowserShot
2) Simulation in different browsers without installation: creates screenshots of your web design in different browsers. E.g. Browser Photo, AnyBrowser.com,Litmus
3) Unit-testing framework: simulates the javascript execution environments for a variety of browsers. E.g. cross-check library
4) JS library: called by page code and shields the cross-browser issues. E.g. Ext library, XLibrary
Current JS debug is designed for specified browser as extension or add-in. Programmer need use different debugger in different browser to debug JS code .
The core ideas of our invention are as below:
1) Provide a communication channel to make multiple debugger are connected for debugging information exchanging.
2) Provide a hook handling mechanism for communicating the debugging in different browsers at runtime.
Control flow policies to sync the browser debugging process for watched variables
Comparison of variables and expressions to provide possible hints of browser compatible issues
3) Provide event simulation from one browser to another which enables user to j...