3 ms·
OK, I shouldn't have led with that number. If I had first told them about the problem 4 months ago, then of course it would be too soon to expect a solution. B
by mwcampbell 5y ago
OK, I shouldn't have led with that number.
If I had first told them about the problem 4 months ago, then of course it would be too soon to expect a solution. But as I wrote further down in the OP, I first contacted them about this roughly 18 months ago. As far as I can tell, they haven't done anything about it in all that time. And though I was previously in contact with the product manager, it has been 4 months since the last time he wrote to me, despite my recurring requests for an update.
Also to be clear, I didn't choose to escalate this now because it has been 4 months. The trigger was Cloudflare's "Impact Week", which included a blog post about their Flarability employee resource group.
- ipv6ipv4 5y agoIf my understanding is correct, Cloudflare first released Browser Isolation 4 months ago. If my experience in the industry is relevant, they just barely released an MVP to get ‘something out the door’. I don’t know where accessibility is on their feature backlog (for all I know, maybe it isn’t) and I understand your point but I don’t think that 4 months is a long time for these things.