[–] 1 point 2 months ago

Table with of fixed issues, including one title "WebStorm slow as hell"

Found this issue's title funny, and I appreciate the last dev's honest reply:

Thanks for the follow-up, and I’m sorry this issue was left unresolved for so long.

I took another look at it, and the problem has now been fixed, and the fix will be available in 2026.3 and 2026.2.3 :)

Unfortunately, with a large number of issues in the tracker, some older reports can remain under the radar much longer than they should. I understand how frustrating that can be, especially after waiting for years.

Thank you for reporting the issue and for providing a reproducible case — it was still valuable in getting this fixed.

  • source
  •  

    You can now jump to a CSS custom property's definition from within the var() function in style rules.

    On clicking the arrow here:

    You get jumped to where it's defined, and it's briefly highlighted.

    The events tooltip in the Inspector now shows a badge besides custom events, making it easier to differentiate them from built-in events.

    I think it's the "User-defined" badges I circled:

    Full release notes

    [–] 58 points 1 year ago (23 children)

    The post on Mastodon has a screenshot of the post edit history:

    Screenshot of a forum post, showing the versions before and after an edit. The sentence "I am queer, I am technically a furry too" was edited into "I am technically a furry too"

    And a copy-pasted response from a moderator (the most relevant bit):

    So in my opinion, if your intention was to show political support for diversity, you should avoid using this flag. This will allow us to refuse the use of a flag for instance saying 'non-queer', If we allow your flag, then we have to admit also other similar political flags, both supporting and opposing diversity.

  • source
  • parent
  • context
  • [–] 1 point 1 year ago*

    The silent keys part were a disappointment, it is way louder than the previous one (had cherry MX silent keys). However, the rest is pretty nice.

    Did you try O-rings? They dampen the sound of the keycap hitting the base of the keyboard.

    https://www.gloriousgaming.com/en-eu/products/glorious-mx-o-ring-switch-dampeners

    Maybe it won't matter with those switches, but they also helped with the switch actuation of my MX Blues. I noticed some high-pitch sound from the springs, and that also got dampened.

  • source
  • parent
  • context
  •  

    I'm posting this in case it helps anyone, but also for a sanity check (anyone has a better solution?).

    My issue - using 3rd party packages and SCSS (and the solution in the docs)

    Using Bootstrap as an example:

    Running php bin/console importmap:require bootstrap doesn't import SCSS.

    The easy provided alternative is installing as Composer package with composer require twbs/bootstrap, and importing the SCSS from there. This happens to work for Bootstrap, but may not be an option for others (there may not be a composer package)

    My alternative

    CSS

    1. Install (at least these) third party packages using npm like usual.
    2. In the app's SCSS file, import using the relative path to the node_modules's bootstrap: @import '../../../node_modules/bootstrap/scss/bootstrap';

    JS

    1. In config/packages/asset_mapper.yaml add the path specifically for the third-party package to be included. My file is looking like this:
    framework:
        asset_mapper:
            # The paths to make available to the asset mapper.
            paths:
                - assets/
                - node_modules/bootstrap/dist/js
            excluded_patterns:
                - 'assets/styles/scss/**/*'
            missing_import_mode: strict
    
    when@prod:
        framework:
            asset_mapper:
                missing_import_mode: warn
    
    
    1. In importmap.php add the path ( and with entrypoint set to true). This only works because of the previous step.
    
    return [
        'app' => [
            'path' => './assets/app.js',
            'entrypoint' => true,
        ],
        // ...
        'bootstrap' => [
            'path' => './node_modules/bootstrap/dist/js/bootstrap.bundle.min.js',
            'entrypoint' => true,
        ],
    ];
    
    1. Import in the template as usual
    {% block importmap %}
        {{ importmap([
            'bootstrap',
            'app',
        ]) }}
    {% endblock %}