Closed
Bug 1199477
Opened 10 years ago
Closed 10 years ago
Incorrect Browser Name in Compatibility Data
Categories
(developer.mozilla.org Graveyard :: BrowserCompat, defect)
developer.mozilla.org Graveyard
BrowserCompat
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmedley, Unassigned)
Details
(Whiteboard: [bc:infra])
What feature should be changed? Please provide the URL of the feature if possible.
==================================================================================
The browser named 'Chrome Mobile' should be removed form the compatibility data. http://browsercompat.herokuapp.com/browse/browsers/5
What problems would this solve?
===============================
'Chrome Mobile' is a meaningless label. Android and iOS use different rendering engines for mobile.
Who would use this?
===================
n/a
What would users see?
=====================
n/a
What would users do? What would happen as a result?
===================================================
n/a
Is there anything else we should know?
======================================
As a separate action item, me or one of the other Chrome writers need to update the Chrome Page (https://developer.mozilla.org/en-US/docs/Glossary/Google_Chrome) to reflect that Chrome on iOS shares its rendering engine with the platform.
Updated•10 years ago
|
Component: General → BrowserCompat
Comment 1•10 years ago
|
||
"Chrome Mobile" was deleted on 2015-08-28 [1]. "Chrome" is now "Chrome for Desktop" [2], joining "Chrome for Android" [3].
Compatibility data for browsers on iOS will be collected under "Safari for iOS" [4] for now. The Chrome page on MDN [5] includes the phrase "Note that the iOS version of Chrome uses that platform's rendering engine, not Blink.".
[1] https://browsercompat.herokuapp.com/api/v1/historical_browsers/25
[2] https://browsercompat.herokuapp.com/browse/browsers/3
[3] https://browsercompat.herokuapp.com/browse/browsers/4
[4] https://browsercompat.herokuapp.com/browse/browsers/15
[5] https://developer.mozilla.org/en-US/docs/Glossary/Google_Chrome
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Keywords: in-triage
OS: Other → All
Hardware: Unspecified → All
Whiteboard: [specification][type:change] → [bc:infra]
Updated•5 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
•