This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
It would be very useful to be able to include functioning examples – as on http://www.html5rocks.com/en/tutorials/webaudio/intro/#toc-volume, for example. This would be problematic to do securely: non-sysop users must not be able to add arbitrary code to a page but, of course, if a page is only editable by sysops, it can't be updated by normal users. Maybe this extension would be useful: Extension:Secure HTML: http://www.mediawiki.org/wiki/Extension:Secure_HTML It might also be desirable to make it possible to include external resources iframe-style, for example as per Extension:Include http://www.mediawiki.org/wiki/Extension:Secure_HTML, but this would also pose security problems.
This is something that is being talked quite a bit about here and there. We should surely do it the only thing is figuring out the best way. Some are saying that we are going to try and port Dribble, if I recall correctly, to use for example code. I'm not sure if we should be doing inline examples when linking out to another area that is singular for demo's would keep things centralized. Inline examples do have the benefit of not using more resources while also being pretty static once they are set so not much upkeep. Any other thoughts?
I guess you mean dabblet, Garbee. I love the previewers there, those would be an awesome feature to have. Two issues come to mind, revisions and security. Revisions would be nice to have in case some change breaks the code or in case of vandalism. Security is obvious, we can't allow random HTML with <script> etc. I thought about using MediaWiki as a solution, possibly using a seperate namespace e.g. "Snippets:". We would automatically have the revisioning and maybe we could set that namespace so, that admins must confirm the edits (I don't know the patroling feature of MW that good). If that doesn't work there would have to be some automatic filter that excludes certain tags. When the reader clicks on the "run that code" button/link, the example could be rendered in a layer using an iframe, the source would be somehow pulled from that Snippet:Something article. Would be nice if could be directly integrated into the semantic forms, but my knowledge of those is even more limited. :) Just an idea, hopefully some other people have more to add. I'll maybe take a closer look at MW plugins programming etc.
Reverting this bug's platform to All, as experience happens on all platforms.
Would like to know if there can be support for compatibility tests for features with spotty implementations, or if that should be handled separately, e.g. w/Modernizr. Would like users to get "this feature doesn't work in your browser version" messages along with recommended alternatives.
We have Dabblet now working. We are going for the front-end integration work. Reports relating to that will now be handled in their own project on the new issue tracker hosted at http://project.webplatform.org . (Still hasn't been made as of the time of writing, but will be made soon.)