Author Topic: Namespacing SafePrice CSS  (Read 7093 times)

0 Members and 1 Guest are viewing this topic.

Offline s2tephen

  • Newbie
  • *
  • Posts: 1
Namespacing SafePrice CSS
« on: August 13, 2018, 10:05:51 PM »
With the new v12.0.903 release of SafePrice, the extension now injects its own CSS into the page, in particular an .animate class that adds a z-index of -9999. This is pretty unfortunately named, since .animate is a common utility class name, and so certain websites will break with the extension enabled. Would it be possible to namespace the SafePrice CSS to minimize these unintended side effects?

Here's a minimal repro (try accessing this page with SafePrice enabled/disabled): https://bevel-anchovy.glitch.me/

Offline prokopes

  • Avast team
  • Jr. Member
  • *
  • Posts: 26
Re: Namespacing SafePrice CSS
« Reply #1 on: August 15, 2018, 01:30:54 PM »
Hi and thanks for reporting this problem, we will fix it asap.

Sorry for any inconvenience.

Offline Chuck Miller

  • Newbie
  • *
  • Posts: 2
Re: Namespacing SafePrice CSS
« Reply #2 on: August 15, 2018, 04:21:58 PM »
Thanks for looking into this and getting corrected!  We are a software developer that provides a SAS to approx 650K users.   Starting on 8/7/18 we started receiving an abundance of new calls regarding issues with people using our software that certain icons/functions/features were "missing" from our application making it unusable.   We've tracked it down to an issue with Google Chrome and the "SafePrice" extension (we have not tested the Microsoft Edge extension yet).    What we have found is that when we disable that, our application functions properly (Note: We do not need to disable the A/V browser protection, just the SafePrice extension).   Our developers have researched and found (and I guess you just confirmed this) that your software is injecting CSS into the web page wherever we use an animation and breaking it. 

What's your update/release schedule?  What kind of time frame would we generally look at for something like this to be corrected?  We'd hate to keep telling people to turn this off or have to work around this. 

Thank you!

Chuck

Offline prokopes

  • Avast team
  • Jr. Member
  • *
  • Posts: 26
Re: Namespacing SafePrice CSS
« Reply #3 on: August 17, 2018, 10:13:21 AM »
Hi Chuck, this problem should be fixed as of today.

Offline Chuck Miller

  • Newbie
  • *
  • Posts: 2
Re: Namespacing SafePrice CSS
« Reply #4 on: August 20, 2018, 07:26:13 PM »
Thanks!  Initial tests on our end confirm.   We will validate in the field now! 

Chuck