WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
178758
Remove the support for JPEG2000
https://bugs.webkit.org/show_bug.cgi?id=178758
Summary
Remove the support for JPEG2000
Said Abou-Hallawa
Reported
2017-10-24 15:57:39 PDT
From
http://caniuse.com/#search=jpeg2000
, Safari is the only browser which supports JPEG2000. Because no other browser is adopting JPEG2000, then there's no real reason for WebKit to keep exposing it.
Attachments
Patch
(7.01 KB, patch)
2017-10-24 18:46 PDT
,
Said Abou-Hallawa
darin
: review-
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2017-10-24 15:58:29 PDT
<
rdar://problem/35161822
>
Said Abou-Hallawa
Comment 2
2017-10-24 18:46:12 PDT
Created
attachment 324771
[details]
Patch
Sam Weinig
Comment 3
2017-10-25 08:03:44 PDT
This seems like this should be runtime configurable for clients of the WebKit API that want to continue supporting JPEG2000.
mitz
Comment 4
2017-10-25 10:04:56 PDT
(In reply to Sam Weinig from
comment #3
)
> This seems like this should be runtime configurable for clients of the > WebKit API that want to continue supporting JPEG2000.
And not drop support for clients that linked against a version of WebKit hat had support.
Said Abou-Hallawa
Comment 5
2017-10-25 12:02:46 PDT
(In reply to mitz from
comment #4
)
> (In reply to Sam Weinig from
comment #3
) > > This seems like this should be runtime configurable for clients of the > > WebKit API that want to continue supporting JPEG2000. > > And not drop support for clients that linked against a version of WebKit hat > had support.
I filed
https://bugs.webkit.org/show_bug.cgi?id=178821
.
Michael Catanzaro
Comment 6
2018-04-24 12:50:40 PDT
This is causing web compat issues for other ports, see
bug #180995
Michael Catanzaro
Comment 7
2018-08-06 12:56:30 PDT
(In reply to Said Abou-Hallawa from
comment #0
)
> From
http://caniuse.com/#search=jpeg2000
, Safari is the only browser which > supports JPEG2000. Because no other browser is adopting JPEG2000, then > there's no real reason for WebKit to keep exposing it.
Also
bug #186272
I think we will have to add JPEG2000 support to GTK and WPE (not really desired) unless Safari drops it.
Said Abou-Hallawa
Comment 8
2018-10-26 11:42:05 PDT
We saw washingtonpost.com uses JP2000 images recently. So I think it is okay to keep the support for now and not to fix this bug.
Michael Catanzaro
Comment 9
2018-10-26 12:27:58 PDT
Well a *lot* of websites are (or were recently) sending JP2000 images (dell.com, kmart.com, I think perhaps amd.com (though this one is sending weird PNGs too so not certain). It's a significant web compat issue for us right now. We need to either: (a) Remove support from Safari, temporarily breaking these websites in Safari (b) Add support to WPE/GTK We had been expecting you to do (a), so if that's no longer the plan, we'll need to work on (b).
Michael Catanzaro
Comment 10
2018-12-18 13:13:44 PST
Adrian discovered every instance of JPEG 2000 images I'm aware of are on websites using Akamai Image Manager. This affects both images with the .jpg extension and also .png; the images seem to be reencoded without changing the filename. It only sends JPEG 2000 images for websites that include Safari without Chromium in the user agent. We currently intend to implement support for JPEG 2000, but if Apple still wants to remove it, probably working with Akamai Image Manager would be the first step. Sample JPEG 2000 images:
https://www.angieslist.com/sites/all/themes/altheme/images/home-hero-overlay.png
https://www.amd.com/system/files/styles/992px/private/65942-ryzen-threadripper-pib-ces-front-facing-1260x709_4.png
https://i.dell.com/sites/csimages/Banner_Imagery/all/25957-laptop-inspiron-14-5481-desktop-3670mt-monitor-d3218hn-2800x944.jpg
https://www.akamai.com/us/en/multimedia/images/article/akamai-image-manager-overview-image.jpg?imwidth=1366
Michael Catanzaro
Comment 11
2018-12-18 13:16:33 PST
Repurposed
bug #186272
to implement JPEG 2000 for non-Apple ports. (If Safari will be removing JPEG 2000 support, please let us know so we don't have to do this!)
Adrian Perez
Comment 12
2022-08-30 01:30:05 PDT
Any chance of Apple removing JPEG2000 from WebKit? Recently we have run into two issues (
bug #244528
and
bug #244529
) and I would rather remove the code than fixing it, giving the marginal usage the format has. From the links mentioned by Michael in
comment 10
, the ones which still load no longer serve JPEG2000 images. The IKEA website was also serving JPEG2000 to WebKit based browsers at some point, but as far as I can see it seems to be using WebP these days.
Said Abou-Hallawa
Comment 13
2022-08-30 14:33:08 PDT
Pull request:
https://github.com/WebKit/WebKit/pull/3824
EWS
Comment 14
2024-02-02 00:30:05 PST
Committed
273978@main
(78cb9d96aa82): <
https://commits.webkit.org/273978@main
> Reviewed commits have been landed. Closing PR #3824 and removing active labels.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug