Closed
Bug 1199483
Opened 10 years ago
Closed 9 years ago
Implement Correct Labels on Chrome Browser Table
Categories
(developer.mozilla.org Graveyard :: BrowserCompat, defect)
developer.mozilla.org Graveyard
BrowserCompat
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jmedley, Unassigned)
References
Details
(Whiteboard: [bc:infra][bc:front][bc:milestone=plane])
What feature should be changed? Please provide the URL of the feature if possible.
==================================================================================
The version of Chrome identified as 'current' is actually a development version. http://browsercompat.herokuapp.com/browse/browsers/3
What problems would this solve?
===============================
Leaving this as is may be potentially misleading to new Web Developers.
Who would use this?
===================
All developers looking for information about Chrome.
What would users see?
=====================
Something like this would be nice:
46 (canary)
45 (beta)
44 (current)
What would users do? What would happen as a result?
===================================================
Developers would have correct information about the available Chrome development channels.
Is there anything else we should know?
======================================
I left off one thing. We need this labeling for Chrome for Android (http://browsercompat.herokuapp.com/browse/browsers/4) and Android Webview (http://browsercompat.herokuapp.com/browse/browsers/16) as well.
Updated•10 years ago
|
Component: General → BrowserCompat
Updated•10 years ago
|
Updated•10 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•10 years ago
|
||
It is currently possible to update this version information through the API, but this is difficult and not the general solution. The desired workflow is that domain experts use the contribution and moderation interface to update version information as new versions are released. If possible, I'd like to wait until the prototype C&M interface is ready, and test this use case against it.
Updated•10 years ago
|
Mentor: jwhitlock
Comment 3•10 years ago
|
||
the Plane milestone is the one targeted to open the C&M interface to the public, we need to make sure we had fixed this before reaching that milestone.
Depends on: 1240101
Whiteboard: [bc:infra][bc:front] → [bc:infra][bc:front][bc:milestone=plane]
Updated•9 years ago
|
Mentor: jwhitlock
Comment 4•9 years ago
|
||
The BrowserCompat project is canceled. See https://github.com/mdn/browsercompat for current effort. Bulk status change includes the random word TEMPOTHRONE.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•6 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
•