Re:Google’s approach to replacing the cookie is drawing anti...
by gcblkjaidfj on Tuesday February 09, 2021 @05:23PM
(#26083219)
> The reasons were stated repeatedly. They rewrote the mobile browser engine
*this have nothing to do with my comment*
I am talking two or three iterations AFTER that. please, stop commenting long posts where you have no idea.
yes, mozilla moved to a new engine. Before that they moved to a new extension format. etc etc etc.
All the extension developers worked on the ports already, *THEN* mozilla, only for mobile, enabled "recommended extensions" which was fine. Until they DISABLED the non-recommended (not non-updated to the new tech).
It have nothing to do with technology. In fact I have many of those extensions working on my phone by fiddling with their whitelist urls. No problem running them AT ALL.
*this have nothing to do with my comment*
I am talking two or three iterations AFTER that. please, stop commenting long posts where you have no idea.
yes, mozilla moved to a new engine. Before that they moved to a new extension format. etc etc etc.
All the extension developers worked on the ports already, *THEN* mozilla, only for mobile, enabled "recommended extensions" which was fine. Until they DISABLED the non-recommended (not non-updated to the new tech).
It have nothing to do with technology. In fact I have many of those extensions working on my phone by fiddling with their whitelist urls. No problem running them AT ALL.
This is political.