New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 259681 link

Starred by 2 users

Issue metadata

Status: Fixed
Last visit > 30 days ago
Closed: Jul 2013
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Launch-OWP
Launch-Accessibility: ----
Launch-Exp-Leadership: ----
Launch-Leadership: ----
Launch-Legal: ----
Launch-M-Approved: ----
Launch-M-Target: ----
Launch-Privacy: ----
Launch-Security: ----
Launch-Test: ----
Launch-UI: ----
Rollout-Type: ----

Sign in to add a comment

Remove support for default touch icons.

Project Member Reported by, Jul 12 2013

Issue description

(See for an overview)

Change description:
 I intend to remove support for default apple touch icons. We will continue to support touch icon declared through the <link rel="apple-touch-icon(-precomposed)"> tag.

 This feature is wasting bandwidth, data plan and battery on mobile devices, as only 8.4% of requests for /apple-touch-icon.png and /apple-touch-icon-precomposed.png are 200

 The only specification for this feature is apple's Safari documentation:

Changes to API surface:
 Page not containing a <link rel="apple-touch-icon(-precomposed)"> tag will no longer trigger a notification for touch icon with the default touch icons.

Public standards discussion: N/A

Support in other browsers:
Internet Explorer: Unknown
Firefox: Unknown
Safari: Yes
Opera: Unknown

Project Member

Comment 1 by, Jul 17 2013

The following revision refers to this bug:

r154413 | | 2013-07-17T18:51:51.164090Z

Changed paths:

Disable default touch icons handling.

When no link rel=apple-touch-icon is present on a page, mobile chrome currently
sends requests for apple-touch-icon.png and apple-touch-icon-precomposed.png. A
very large majority of those requests fail with a 404. To save battery and data
plan, this CL disable those requests. Clients should use link rel=icon instead.

We can't turn of TOUCH_ICON_LOADING because we still want to support link

 Resubmitted after removing the test checking for this behavior in chromium:
BUG= 258963 , 259681 

Review URL:

Comment 2 by, Jul 18 2013

Status: Fixed

Sign in to add a comment