A simple CSS rule to automatically calculate this is very welcome.
I'm not sure I like the name "pretty" for the second rule though. If they have to expose the algorithm (first-fit vs Knuth-Plass), I'd rather they choose more descriptive names.
5,684 karma · joined November 8, 2011
A simple CSS rule to automatically calculate this is very welcome.
I'm not sure I like the name "pretty" for the second rule though. If they have to expose the algorithm (first-fit vs Knuth-Plass), I'd rather they choose more descriptive names.
User karma isn't factored into the site's sorting algorithms. Post score is, and that influences karma, but not the other way around.
edit: On reflection, you may have been referring to the ability to post, rather than the popularity of the post. In that case, the misunderstanding was mine.
It's still not convenient, but it's a much smaller hurdle to overcome.
No, it's definitely not. You can read the byte length more directly in JS, and use that to inform if more text is allowed or not.
const encoder = new TextEncoder();
const currentBytes = encoder.encode(inputStr).byteLength;
But the maxlength attribute is at best an approximation. Don't rely on it for things like limiting length for database fields (not that you should trust the client anyway).I tested both AdGuard and uBlock Origin in MV3 for a while, and they seemed fine to me. Adguard's had less friction due to opting sites into cosmetic filtering by default.
True, but Vulkan is largely a continuation of Mantle which released two years before DX12.
Once scrutinized, these phenomena are almost always explained by humans misinterpreting their instruments (either machine readout, or their own eyes).
Honestly, you wouldn't believe how many people report _the moon_ as a UFO because it shows up in an odd place, gets distorted by unique atmospheric conditions, and can appear in different shapes and sizes (moon phase and proximity to Earth).
These people aren't idiots. Their brains evolved to recognize patterns as a survival mechanism. Arguably their pattern recognition is stronger than everybody else's. But when you factor in lack of familiarity with the scientific method, or inclination towards spirituality, or a simple willingness to believe in extraterrestrial life, it's not uncommon to hear stories about ghosts, angels, and aliens.
These stories do not stand up to inquiry. They have been tested time and time again and always fall apart under scrutiny. The reason that Bigfoot photos are always blurry isn't because he's camera shy - it's because when the photos are not blurry, we can clearly see it's not Bigfoot.
NB: I have no problem with believing in alien life in terms of say the Drake equation (statistically, it's probable!). I just find it highly unlikely of such a visitor reaching Earth.
I get that there's always one of today's lucky 10,000, but I think a certain threshold of obscureness is reasonable. It wouldn't make sense to submit the Linux Kernel project, or Mozilla Firefox without any news.
Maybe I'm overestimating how well-known ReactOS is, though.
>There have been click-baity news reports stating that “Google Removes ‘Don’t Be Evil’ Clause From Its Code of Conduct” but that is not entirely accurate.
>Google has not removed that clause. Google has removed it from the preface, resulting in more attention to the word respect. But it still remains at the end of the document as before.
edit: This was in response to the parent's original comment, prior to the edit.
https://www.howtogeek.com/wp-content/uploads/2021/06/2-sign-...
edit: Some comments below suggesting this is mistaken. Sorry, I hadn't noticed that in the past.
https://www.howtogeek.com/735152/how-to-turn-off-the-sign-in...
The Browser Launch feature says that Firefox always waits for extensions to load network requests whereas Chrome gives an option to wait via a setting. So in this case, you're trading performance (parallelizing the work) for privacy (may not catch a tracking request). It's a tradeoff I'm sure many are willing to make, but I like that Chrome offers the setting. I tend to err towards performance, myself.
WebAssembly says it isn't used - not because it isn't available - but because it would add an extra permission to the manifest. That is to say, Chrome informs you of this when installing extensions and Firefox doesn't. That's a minor implementation detail at best, and I think a case can be made that providing more granular scopes is a positive thing.
Then pre-fetching. Are they really disabling a major performance feature by default? I've used pre-fetching to good effect when the browser's resource scanner ran at the wrong times. The option should exist but this is a terrible default.
The other features are more reasonable. HTML filtering could be useful for adversarial sites like Twitch.tv that actively fight adblockers. Storage Compression seems like a useful optimization if you have a lot of extensions installed that populate IndexedDB. I'm assuming it's caching those values rather than doing a "first time setup" every time a new private window is launched.
I'll readily admit there may be more intent behind these features than is expressed in these blurbs, but on initial glance I wouldn't say anything here is critical. The pre-fetching one in particular seems like a negative.
Boy do I know that one. Intermittent issues are so much harder to debug. Getting a frequent test case often means the difference between solving a bug in an afternoon, or letting it live on as a GitHub issue for years, only to be bumped every few months by a comment that adds no new information at all.
I think it's very clear that adblockers are still possible in MV3, despite concerns.
https://chrome.google.com/webstore/detail/adguard-adblocker-...
https://chrome.google.com/webstore/detail/ublock-origin-lite...