You want suckage in a web browsers.... I switched to chrome, because firefox made the bookmark backup files undecodable by standard tools! That is they used a in-house compression variant. That meant the only way to decode them was to use the firefox program itself. Not exactly a good way of making 'backups' of something, that you may want to extract say ten years later!
After months of discussion someone extracted that code and made a separate standalone firefox XML uncompresser, but by then I'd switched. On Mon, Jan 16, 2017 at 4:32 PM, Matthew D. Fuller <[email protected] > wrote: > > On Sat, Jan 14, 2017 at 12:10:31PM +0000 I heard the voice of > Richmond, and lo! it spake thus: > > > > But there is still an intermittent problem with google chrome's menu > > button (that is the three virticle dots top right of google chrome) > > sometimes it works, sometimes it doesn't. If I click on something > > else, or open a new tab, sometimes that makes it work/stop working. > > There are discussions from time to time about weird sticky keyboard > focus issues, commonly around chrome and firefox. I'm not sure we've > seen much mouse-related oddity. > > Now, that said, chrome has never been anything but weird and flaky in > all sorts of ways for me. I only have it around for testing stuff; if > I had to use it as my day to day browser, I'd have given up on using > the web a long time ago. I'm pretty sure web browsers in general > exist principally to provide an object lesson on the law of > conservation of software suckage. > > > -- > Matthew Fuller (MF4839) | [email protected] > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ > On the Internet, nobody can hear you scream. > >
