Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

core: rename uses-webp-images to modern-image-formats #12535

Merged
merged 4 commits into from
May 25, 2021

Conversation

brendankenny
Copy link
Member

@brendankenny brendankenny commented May 21, 2021

part of #11866

With webp now being mainstream and AVIF and jpeg XL on their way, we're renaming the uses-webp-images audit to better reflect its goal, which is to suggest using next-gen *ahem* "modern" image formats (via e.g. <picture>), even if they're not available everywhere yet. See #12295 for details.

We didn't totally agree on this name yet, so we can decide here, which will be fun, and then I'll update GoogleChrome/lighthouse-stack-packs#63 to match. done

@brendankenny brendankenny requested a review from a team as a code owner May 21, 2021 21:37
@brendankenny brendankenny requested review from adamraine and removed request for a team May 21, 2021 21:37
@google-cla google-cla bot added the cla: yes label May 21, 2021
@brendankenny brendankenny mentioned this pull request May 21, 2021
17 tasks
@connorjclark
Copy link
Collaborator

would prefer "(uses-)?modern-image-formats"

@brendankenny
Copy link
Member Author

would prefer "(uses-)?modern-image-formats"

"uses" is a no-go based on "Naming: Audit ID".

To me "modern" sounds a little more mainstream. Like I expect something that's part of the "modern web" to work on the majority of evergreen browsers. I don't feel strongly about modern vs next-gen, though.

Copy link
Member

@adamraine adamraine left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 to modern-image-formats

https://www.thesaurus.com/browse/modern: with-it-image-formats 👀?

/**
* @return {LH.Audit.Meta}
*/
static get meta() {
return {
id: 'uses-webp-images',
id: 'next-gen-image-formats',
title: str_(UIStrings.title),
description: str_(UIStrings.description),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably update the docs to mention AVIF at some point. Maybe deprecate the WebP article and write a new one?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably update the docs to mention AVIF at some point. Maybe deprecate the WebP article and write a new one?

👍 thats #12295

@brendankenny
Copy link
Member Author

Note that the audit title has been "Serve images in next-gen formats" since Lighthouse 2.7.0, changed in #3985. This PR is only for the audit ID.

Humorously from #3985 and #3557 it appears @patrickhulce has long been in favor of "next gen" but @paulirish was against it, though later decided he was fine with the name :)

@brendankenny
Copy link
Member Author

https://www.thesaurus.com/browse/modern: with-it-image-formats 👀?

haha.

In #3985 (comment) Paul suggested 2010-era for the webp audit. AVIF support landed in Chrome 85, so I guess 2020-era-image-formats would be accurate now and good for a few years before needing another rename :)

@patrickhulce
Copy link
Collaborator

Humorously from #3985 and #3557 it appears @patrickhulce has long been in favor of "next gen" but @paulirish was against it, though later decided he was fine with the name :)

Haha, oooooh "superior" and "performant" -- hardworking, alphamale, jackhammer, merciless, insatiable image formats 😈

I prefer next-gen, but I'm also fine with modern since it appears the majority has already spoken.

@brendankenny
Copy link
Member Author

OK, unless he says otherwise, I'm going to assume @paulirish would also prefer modern-image-formats since he wrote "next-gen" very reluctantly in #11866 and made sure to include the modern even though no one had said that out loud at the time :P

modern-image-formats it is

@brendankenny
Copy link
Member Author

(all the stack-pack strings will get readded in the next dump->import cycle since only their name changed, not their content)

@brendankenny brendankenny changed the title core: rename uses-webp-images to next-gen-image-formats core: rename uses-webp-images to modern-image-formats May 21, 2021
@addyosmani
Copy link
Member

Fwiw, +1 on modern-image-formats :)

@@ -25,13 +25,13 @@ const str_ = i18n.createMessageInstanceIdFn(__filename, UIStrings);

const IGNORE_THRESHOLD_IN_BYTES = 8192;

class UsesWebPImages extends ByteEfficiencyAudit {
class NextGenImageFormats extends ByteEfficiencyAudit {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
class NextGenImageFormats extends ByteEfficiencyAudit {
class ModernImageFormats extends ByteEfficiencyAudit {

and co

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whoops, thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants