1734432 - Investigate potential intervention for https://spark.adobe.com/page/

Status: RESOLVED WONTFIX

(Web Compatibility :: Interventions, enhancement)

Description

[Dennis Schubert [:denschub]]

See the linked WebCompat bug for context.

To pass as Chrome, we have to to undefine window.InstallTrigger and set window.chrome to something truthy. I'm not sure if this breaks something, but I can't easily test that without building the intervention anyway, so it's worth looking into.

Comment 1

[Dennis Schubert [:denschub]]

Given the comments in the web-bug, let's unschedule this for now.

Comment 2

[Dennis Schubert [:denschub]]

Let's check this again to see if we can get an intervention into 103.

Comment 3

[Dennis Schubert [:denschub]]

Okay, I'm not only going to de-scope this for 103, I'm actually closing this as a wontfix.

For context: the issue we're trying to solve here is not a critical breakage. Instead, it's just about the scrolling being slower than expected. This is ultimately due to a Firefox-only codepath that handles the scroll event differently. It's certainly a bit irritating, but that's about it.

Shimming InstallTrigger and window.chrome works to "fix" the scrolling issue. As in, it's scrolling faster with that, and scrolling is consistent with Chrome - but that scrolling is still a custom scrolling logic, and with the workaround in place, it actually feels too fast as compared to the rest of web content in Firefox.

When spoofing as Chrome, there are a bunch of exceptions and potential code-paths that worry me a bit. And since Adobe Express (the new name for Spark) is a site builder with a large number of sites in it, we can't possibly test all the sites to make sure this doesn't break another site.

Ultimately, this would be a medium-risk patch for a non-breaking "this just feels weird" UX, that would still feel weird - just a different kind of weird - with the intervention.

Comment 4

[Ryan VanderMeulen [:RyanVM]]

Have we attempted to contact Adobe about this issue? I ran into this bug today on another Adobe site and it's a pretty bad experience.

Comment 5

[Dennis Schubert [:denschub]]

We contacted them, about a year ago. We've received acknowledgement, but no further action. I'll ping them back.

Ryan, can you share the URL to the site for reference?

Comment 6

[Ryan VanderMeulen [:RyanVM]]

It was on express.adobe.com. I'll share the link with you privately.