https://www.firstdirect.com blocked

[cannonmc]

Up until this weekend this had been a straightforward site to reach, whichever version of PM I used.

Over the weekend the online section was blocked, then today the main page https://www.firstdirect.com is blocked.

I am using Win7 64bit and latest PM. Is this just another example of people forgetting we might prefer something other than Google or MS for a proper browser.

I have written to them but suspect will get another 'standard' answer

[Gemmaugr]

The main page you linked works for me.

[Moonchild]

"blocked" looks like it's another case of a really really poor implementation of a fake-modal GDPR consent dialog.
You should just give them a call and complain. There's no way for us to get in touch with them to report this, since their only means of contact are for existing customers, through the "app" on mobile or after logging in on the non-functioning website.
You can work around it by using an ad blocker and a GDPR "I don't care about cookies, just use them" annoyances filter list, or similar.

[cannonmc]

They did have the grace to ring me. They tried to put the blame on PM. I pointed out that a rock solid link does not get blocked in two steps on one weekend.

I told them I knew what had happened. They changed their end and missed out the 'little people'

It worked on Waterfox which is where I wrote to them...for now. But I have been raised to a formal complaint.

She said she would keep me informed.

I'll try the work around, thanks

[adoxa]

CSS clip-path doesn't like being border-box, so it's clipping the entire thing. Here's a userstyle workaround.

Code: Select all

@-moz-document domain("www.firstdirect.com") {
  .fd-popup-content {
    clip-path: unset !important;
  }
}

(Something like "Dismiss The Overlay" would also work.)

[Moonchild]

CSS clip-path doesn't like being border-box

Not by itself, no. Seems this is also an open issue for gecko bug #1465988?
Either way that particular bug also provides an immediate potential solution: instead of "unset" like you did, the proper solution would be clip-path: border-box inset(0 0 0 0);

[cannonmc]

It's all back to how it was before, even on PM27. Long message from them and guess what....it's all our fault. They say which browsers are supported (they don't) and they haven't touched anything at their end. I don't believe them.

[Moonchild]

Well maybe they didn't touch anything on their end but the consent dialog is supplied by their data harvesting partner Tealium, so it's likely Tealium changed something (and they are just including whatever content they serve up). And when I say "data harvesting" I mean it. Curiously, their GDPR dialog on their own site works just fine and doesn't seem to have a clip-path specified at all -- not that it needs one, anyway, to be frank.