131–140 of 175 posts
Anyone knows if Tree Style Tab is supported?
An alternative vertical tab bar I discovered some time ago is Tab Center ( https://testpilot.firefox.com/experiments/tab-center ). Although still a little buggy, I switched over from Tree Style Tab. It feels better IMO and I really didn't care about the "tree style" of TST, I just felt the need for a vertical tab bar.
Earlier quoted context omitted.
An alternative vertical tab bar I discovered some time ago is Tab Center ( https://testpilot.firefox.com/experiments/tab-center ). Although still a little buggy, I switched over from Tree Style Tab. It feels better IMO and I really didn't care about the "tree style" of TST, I just felt the need for a vertical tab bar.
Wow, I just tried it, and it's the tab interface I always wanted. More vertical space for reading web pages, and wider tabs to read the tab titles more easily. Why isn't this the default yet?
Looks like accessibility tools (e.g. screen readers) also disable multi-process support as of Firefox 50. I know enough about accessibility APIs and their implementations to guess that it's going to be difficult to modify that code to work efficiently in a multi-process configuration.` Edit: I'm talking about Windows. Don't know about other platforms.
I'm the dev who is responsible for the Windows implementation. It has been quite the... gnarly experience to say the least. We were shooting for 52 for enabling a11y+e10s, but it is increasingly looking like we're going to need to slip to 53.
Earlier quoted context omitted.
Lastpass + Self Destructing Cookies for me :(
I upgraded to the latest version of the LastPass plugin direct from the LastPass site and it seems to work fine. For whatever reason, the one they have listed on AMO is a whole major version behind. https://lastpass.com/lastpassffx/
Earlier quoted context omitted.
that's kind of also a really important use case. "There is no reason to trust this certificate in perpetuity, so pretending it hasn't been compromised over a long period of time would be stupidly insecure. Let's expire it after X months". There is no reason to trust a certificate that's older than a year, for instance, there's been more than enough time for someone to reverse engineer the keys if they wanted. The rea…
> There is no reason to trust a certificate that's older than a year, for instance, there's been more than enough time for someone to reverse engineer the keys if they wanted. Cryptography does not work that way. > It's pretty trivial to set up cert renewal, so why didn't they? That holds true today, with Let's Encrypt; their short expiration date seems to exist largely to force people to automate it, and in that reg…
> Cryptography does not work that way.
But it kind of does. Imagine if we were still using certificates signed with DES and MD5 hashes because they were available perpetually. Certificate expiration at the very least means that whenever you renew you're keeping up to date with whatever vulnerabilities have been exploited in the past 3-5 years.
It also keeps CRLs short and concise as those certificates that have expired do not need to be included.
I like how Firefox multiprocess has evolved and continues to evolve taking measurements into account. When multiprocess was announced several years ago, my main worry was that it would be a Chrome clone with one process per tab and become sluggish like Chrome (my general use of browsers is a minimum of 10 tabs and on certain machines a lot, lot more). Finding a balance between responsiveness, security and stability i…
So I'm happy with this progress even though it may seem slow to some people or that Firefox isn't keeping up with Chrome (the latter is meaningless for my use since Firefox and its extensions provide a lot more).
Earlier quoted context omitted.
> There is no reason to trust a certificate that's older than a year, for instance, there's been more than enough time for someone to reverse engineer the keys if they wanted. Cryptography does not work that way. > It's pretty trivial to set up cert renewal, so why didn't they? That holds true today, with Let's Encrypt; their short expiration date seems to exist largely to force people to automate it, and in that reg…
> There is no reason to trust a certificate that's older than a year, for instance, there's been more than enough time for someone to reverse engineer the keys if they wanted. > Cryptography does not work that way. But it kind of does. Imagine if we were still using certificates signed with DES and MD5 hashes because they were available perpetually. Certificate expiration at the very least means that whenever you ren…
We don't rely on expiration or revocation for that; we rely on clients and servers refusing to use insecure algorithms.
Make Vimperator great again - still no support. :'( Two year old github issue but yet any development to be seen or reported :/
Looks like accessibility tools (e.g. screen readers) also disable multi-process support as of Firefox 50. I know enough about accessibility APIs and their implementations to guess that it's going to be difficult to modify that code to work efficiently in a multi-process configuration.` Edit: I'm talking about Windows. Don't know about other platforms.
I'm the dev who is responsible for the Windows implementation. It has been quite the... gnarly experience to say the least. We were shooting for 52 for enabling a11y+e10s, but it is increasingly looking like we're going to need to slip to 53.
Make Vimperator great again - still no support. :'( Two year old github issue but yet any development to be seen or reported :/
Check out VimFX. It is a very capable substitute.