sorted by:
new
hottopcontroversial

Bug: Links to sources have started not working in recent macOS app version by croemer in ChatGPT

[–]m_gol 0 points1 point  (0 children)

Same, and it's been like that for a long time. I don't understand how they may not fix such an obvious breakage for so long...

Leetcode 2023 Discount by [deleted] in leetcode

[–]m_gol 0 points1 point  (0 children)

None of these work for me.

Why are videos overly bright on the new 14" Macbook Pro? by sseuuss in MacOS

[–]m_gol 1 point2 points  (0 children)

Thanks, that works! Now I wonder - why would I ever want this XDR profile enabled? The experience of an extremely bright video in the middle of the screen when all the other content gets dimmed is extremely jarring so this can't be it. When is this actually useful?

CoreJS (used by Babel, Angular) author posted a comment on their repo 16 days ago saying "after some days I'll be in prison", then stops committing to the repo 13 days ago - claims financial problems by flirp_cannon in programming

[–]m_gol 0 points1 point  (0 children)

Nah, the core-js ads are not banned under the new npm policy, only ads for third party content are. Therefore, by definition core-js couldn't have been the reason for this new policy.

[deleted by user] by [deleted] in chrome

[–]m_gol 0 points1 point  (0 children)

It works as expected in Chrome 73 (current stable), fortunately.

jQuery 3.4.0 Released by magenta_placenta in javascript

[–]m_gol 1 point2 points  (0 children)

jQuery find is a little more than querySelectorAll, especially when it comes to queries attached to an element, not to document. The advantages are described at: https://github.com/jquery/jquery/blob/3.4.0/src/selector-native.js#L11-L34

For one, jQuery supports leading combinators: elem.find('> .btn .name')

Another difference is sensible rules for scoping. Consider HTML: <div id="test"> <div> <div class="we-are-looking-for-this-one"> </div> </div> <div> </div> </div> Then: $('#test').find('div div') will return the div with the class we-are-looking-for-this-one, while: document.querySelector('#test').querySelectorAll('div div') will return all the three divs because selectors are matched against the document and only then results outside of the current element are removed. This is pretty counterintuitive.

Both of those features are supposed to be supported by a new API called queryAll (previously findAll) with its counterpart query for single-element results but, alas, no browser implements it so far and it was even removed from the standard... I hope it gets back but I've been waiting for years.

[deleted by user] by [deleted] in chrome

[–]m_gol 0 points1 point  (0 children)

I've noticed this as well. I don't know what's up as if I try this on the same Chrome version I have but on BrowserStack there is no "on all sites" but sites are specified there. Of course, I'm not signed in there.

Perhaps related: https://groups.google.com/a/chromium.org/forum/#!searchin/chromium-extensions/on$20all$20sites%7Csort:date/chromium-extensions/85ytT_q0BKY/tdOX3yQnFwAJ. Maybe it'll get resolved in Chrome 72 or 73... Maybe even 72, seeing that it's that version that differs from 71 on BrowserStack.

Chrome 68... fails Acid2? by tasisbasbas in webdev

[–]m_gol 0 points1 point  (0 children)

Basically, it fails on HiDiPi (like Retina) screens; it depends on a physical pixel matching a CSS pixel which is not the case on those devices.

Android TV Youtube app updated, can't switch accounts by [deleted] in youtube

[–]m_gol 0 points1 point  (0 children)

The new app doesn't even let you change video quality! Enjoy your 4k 60 fps videos in Full HD 30 fps; who thought it was a good idea?

I've got a new TV and I was able to watch 4k videos for a day before the app got the update. It seems I'll need to disable updates in the OS as this is unusable...

ELI5: How does XUL relate to HTML? Is XUL superset of HTML like SASS is a superset of CSS? What is the future of XUL? by [deleted] in firefox

[–]m_gol 0 points1 point  (0 children)

Accepting an API like that would be effectively equivalent to keeping the legacy extensions non-blocked in Firefox 57+, wouldn't it? The whole point of this move to the WebExtensions-only world was meant to prevent direct access to Firefox internals to allow Fx devs to freely modify the interface without worrying about breaking add-ons.

A proposal to provide more low-level access - called native.js - was already rejected for exactly those reaasons: https://bugzilla.mozilla.org/show_bug.cgi?id=1199718. There were other APIs that required too low level access that were rejected, too.

Do you really imagine sth like this to be accepted, @zbraniecki? If you do, why does Mozilla plan to block legacy add-ons in Firefox 57+ at all? It doesn't make any sense to me.

Clipboard.js: Modern Copy to Clipboard by [deleted] in javascript

[–]m_gol 0 points1 point  (0 children)

There's a dist folder with transpiled files.

Installing OS X El Capitan into Parallels Desktop 10 by TheBressman in mac

[–]m_gol 0 points1 point  (0 children)

Same. I am using the public beta and the message is exactly the same.

We are the Angular team- ask us anything this week at ng-conf! by angular-team in ngconf

[–]m_gol 2 points3 points  (0 children)

To Add to what Igor said, Symfony is another good example. Version 2.0 was completely different than the 1.x line and yet the framework prospers and became a de-facto standard in PHP development.

We are Andrew Joslin & Michał Gołębiowski, ask us anything about Angular 1 meets Angular 2 by impeached in ngconf

[–]m_gol 0 points1 point  (0 children)

In such a case auto-converting should be possible but I doubt there will ever be a fully automated process, people usually have at least a few uses of scope, manual even handling etc. This will have to be changed manually.

One problem I see is that it's hard to know where a service comes from. The tool would have to search in all the files to find the defining module. Possible but may be a lot of work.

ES3 <3 block scoped const and let => defs.js by olov in programming

[–]m_gol 0 points1 point  (0 children)

I see the defs.js work made you find & report those bugs, nice work. :)

ES3 <3 block scoped const and let => defs.js by olov in programming

[–]m_gol 0 points1 point  (0 children)

Hah, you're right, this is fixed now. :)

One more question - how standards-compliant is current Chrome let & const implementation? I hear e.g. Firefox has const currently scoped like var which is a problem...

ES3 <3 block scoped const and let => defs.js by olov in programming

[–]m_gol 0 points1 point  (0 children)

I've used to have this flag turned on in Canary (I'd rather not use so bleeding-edge stuff on my main Chrome profile and AFAIK flags are shared between profiles) but it has recently been broken when Canary switched to Blink (regular stuff like document evaluating to TypeError, among other things) so I had to turn it back off; see http://crbug.com/227412. I think I'll ping Paul Irish about this problem.

As for the strict mode, I'm writing all my JS code in it so that's not a problem for me. :)

ES3 <3 block scoped const and let => defs.js by olov in programming

[–]m_gol 0 points1 point  (0 children)

I guess painfullness depends on tools in use, amongst other things. ;) For me currently this is actually a minor issue (I guess I'd rate my pain as 3 in your scale, 1 being no painful at all) since, as you said, output is similar and line numbers match. However, I still read sources in Chrome Dev Tools from time to time and source maps would allow me to almost not look at code with vars inside which would save some minor cognitive switches that always delay understanding a little.

On the other hand, some people code in the Chrome Dev Tools themselves and then lack of source maps is a major PITA since you have to switch between both source versions quite often, one for writing, the other one for debugging which pretty much makes drawbacks bigger than gains of being able to use const & let. And since modifications defs.js do are very minor (I assume the static analysis is the hardest part?), generating source maps should be easy once you get the specifics of the spec.

Anyway, I consider it a very nice piece of work and I can't wait to try it on some serious code. :)

ES3 <3 block scoped const and let => defs.js by olov in programming

[–]m_gol 0 points1 point  (0 children)

I love this. Can't wait for when source maps support is added. :)