Closed
Bug 742117
Opened 12 years ago
Closed 9 years ago
Warn the user if a demo requires a feature that is not supported on their platform (Touch Events, Orientation, etc.)
Categories
(developer.mozilla.org Graveyard :: Demo Studio / Dev Derby, enhancement)
developer.mozilla.org Graveyard
Demo Studio / Dev Derby
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: openjck, Unassigned)
References
Details
(Whiteboard: [specification][type:feature][specification-comment:3][might-expire][triaged][type:feature][pm-wanted])
A user brought this up in bug 737296. > The first demo "Pinball" does nothing. > The second demo "Help UFO" does nothing unless you guess and try the W-A-S-D keys. > ... > All demos need to do feature detection and warn if required or important > features like device motion and orientation aren't detected. Mozilla > evangelists like Chris Heilmann harp on this, but demos rarely walk the walk. Possible solution: Provide a set of checkboxes for things like "This demo requires a recent mobile browser" and similar. Any other ideas?
Reporter | ||
Comment 1•12 years ago
|
||
Luke also mentioned feature detection.
> We could add feature-detection for the tagged technologies
> to the launch bar and display a notice in the bar for
> unsupported features.
Reporter | ||
Comment 2•12 years ago
|
||
Another good idea from Luke:
> automatically detect user agent and unsupported features.
> Syndicate the notice to the demo author.
Assignee | ||
Updated•12 years ago
|
Version: MDN → unspecified
Assignee | ||
Updated•12 years ago
|
Component: Demos → Demo Studio / Dev Derby
Reporter | ||
Updated•12 years ago
|
Priority: -- → P3
Reporter | ||
Updated•11 years ago
|
Priority: P3 → --
Summary: Demo Studio UX: Warn if a demo requires a certain feature → Warn the user if a demo requires a feature that is not supported on their platform (Touch Events, Orientation, etc.)
Whiteboard: u= c= p= t= s=
Reporter | ||
Comment 3•11 years ago
|
||
Comment 2 is covered in bug 746817. For this feature, see the specification below. What problems would this solve? =============================== Some Demo Studio demos use technologies that only work on certain platforms. For example, as I note above, "Help UFO" only works on mobile browsers. When loaded on the desktop, it cannot be used and appears to do nothing. Who would use this? =================== Users browsing demos would be most affected by this new feature. What would users see? ===================== Users would see a notice if a particular demo does not work on their platform. For example, if a user loaded "Help UFO" on the desktop they would see a notice about the demo only working properly on mobile browsers. If a user loads the same demo in a mobile browser, they should not see the notice. What would users do? What would happen as a result? =================================================== Users would read this notice and, ideally, would not be confused if a demo does not appear to work on their platform. Is there anything else we should know? ====================================== A few different possible solutions to this problem -- feature detection, asking the author what platforms the demo supports, etc.
Whiteboard: [specification][type:feature][specification-comment:3]
Comment 4•11 years ago
|
||
Same question as bug 746817: "technology detection" sounds like a pretty big dev challenge. Do you have any pointers to prior art, or some place else that already does something like this?
Reporter | ||
Comment 5•11 years ago
|
||
Same response. :-) https://bugzilla.mozilla.org/show_bug.cgi?id=746817#c3
Comment 6•11 years ago
|
||
Do something with http://www.browserscope.org/ ?
Comment 7•11 years ago
|
||
(In reply to Luke Crouch [:groovecoder] from comment #6) > Do something with http://www.browserscope.org/ ? Sure... building a DB of platforms vs features are what the compatibility tables on MDN are about. We could make those more machine readable. Or pull them from a source like browserscope. That's more a clerical challenge in keeping the data up to date than a technical one. What I'm saying is that scanning a demo to detect what technologies it uses is a challenge, and why we have tech tags. browserscope doesn't do that for us
Reporter | ||
Comment 8•11 years ago
|
||
I think author-selected tech tags work fine as a way of determining what features are used. The design purist in me would still love feature detection, but it's obviously way out of scope.
Reporter | ||
Updated•10 years ago
|
Severity: normal → enhancement
Whiteboard: [specification][type:feature][specification-comment:3] → [specification][type:feature][specification-comment:3][might-expire][triaged][type:feature]
Reporter | ||
Updated•10 years ago
|
Whiteboard: [specification][type:feature][specification-comment:3][might-expire][triaged][type:feature] → [specification][type:feature][specification-comment:3][might-expire][triaged][type:feature][pm-wanted]
Comment 9•9 years ago
|
||
Demo Studio is being retired from MDN and archived as of end January 2016
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•