Closed Bug 459291 Opened 17 years ago Closed 12 years ago

add or improve fallback in canvas examples

Categories

(Developer Documentation Graveyard :: HTML, defect)

defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: info, Unassigned)

References

()

Details

(Whiteboard: u=webdev p=0 c=HTML)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2pre) Gecko/20081008 Minefield/3.1b2pre Build Identifier: The <canvas> samples should fail simply and consistently in lesser browsers. Reproducible: Always Steps to Reproduce: 1. Visit examples like https://bugzilla.mozilla.org/attachment.cgi?id=273497 and http://developer.mozilla.org/samples/canvas-tutorial/2_1_canvas_rect.html in MSIE 7 and Google Chrome. Actual Results: You get no output and no warning from the fancy canvas text example; the basic canvas demo has a too-specific "You need Safari or Firefox 1.5+ to see this demo" alert(). Both have no fallback within the <canvas> tag. Expected Results: I think all the examples should have a consistent <canvas> fallback, e.g. <p>This example requires a browser that supports the <a href="http://www.w3.org/html/wg/html5/">HTML5</a> &lt;canvas&gt; feature.</p> and, when necessary, a more generic alert(). Don't let this polish request block MDC examples, they are awesome motivators!
I added a _View this example_ link to http://developer.mozilla.org/en/Canvas_tutorial/Basic_usage with this fallback text, it seems to work in FF 3.1, Chrome, and MSIE 7. Maybe do it "right" once and in other examples just have <canvas> Your fallback text here </canvas>
Component: Documentation Requests → Documentation
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
Whiteboard: u=webdev p=0
Component: General → HTML
Whiteboard: u=webdev p=0 → u=webdev p=0 c=HTML
IMHO this is no longer relevant; browsers that don't support <canvas> are incredibly rare now.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.