1161141 - Facebook requires advanced Ad product users to use Chrome (has Web SQL dependency)

Status: RESOLVED INCOMPLETE

(Web Compatibility :: Site Reports, defect)

Description

[Olivier Yiptong [:oyiptong]]

Attachment: image.png

Quoting jterry:

> Facebook requires advanced users (most agencies and brands using Facebook to
> buy ads) to use Chrome. Odd since this would serve to enhance the dominance of
> their largest competitor (for ad dollars and beyond).

Comment 1

[Michael Ellis]

Kdubost - Mind taking a look at this bug and providing a comment?

Comment 2

[Karl Dubost💡 :karlcow]

Do we know if the "Power Editor" requires specific features from Chrome?
This needs diagnosis before doing any outreach.

Comment 3

[Mike Taylor [:miketaylr]]

I'd be happy to do diagnosis, but will need some test creditials (I don't have a FB account), or access to an account with the "advanced Ad product". Someone could email that to me.

Comment 4

[Karl Dubost💡 :karlcow]

I wonder if Harald can help us for the account or put us in contact with the right persons?

Comment 5

[Michael Ellis]

I have a moz test fb account, but no "advanced ad product".  Ping me on IRC (MikeE) or email for the credentials.

Comment 6

[:Harald Kirschner :digitarald]

We checked with our contacts and they are not involved with the ad management interface. It has been Chrome only since it launched.

Comment 7

[Hallvord R. M. Steen [:hallvors]]

Spoofing Chrome gives me a message saying "Power Editor has encountered an error from which it cannot recover cleanly. We apologize that this will result in losing any changes you have not yet uploaded. You can choose to try loading Power Editor again, or reset it then download your account."

Comment 8

[Hallvord R. M. Steen [:hallvors]]

The "power editor" currently depends on Web SQL database.

To support Firefox, they would need to rewrite it to use indexedDB.

Comment 10

[Hallvord R. M. Steen [:hallvors]]

In https://webcompat.com/issues/472 Facebook confirms they are working on it. No ETA, it's complex.

I'll close this Bugzilla bug since it's a cross-browser issue and we have Facebook engineers engaging on Webcompat.com :-D