Category: News

In November 2023, we shared a timeline for the phasing out of Manifest V2 extensions in Chrome. Based on the progress and feedback we’ve seen from the community, we’re now ready to roll out these changes as scheduled.

We’ve always been clear that the goal of Manifest V3 is to protect existing functionality while improving the security, privacy, performance and trustworthiness of the extension ecosystem as a whole. We appreciate the collaboration and feedback from the community that has allowed us – and continues to allow us – to constantly improve the extensions platform.

Addressing community feedback

We understand migrations of this magnitude can be challenging, which is why we’ve listened to developer feedback and spent years refining Manifest V3 to support the innovation happening across the extensions community. This included adding support for user scripts and introducing offscreen documents to allow extensions to use DOM APIs from a background context. Based on input from the extension community, we also increased the number of rulesets for declarativeNetRequest, allowing extensions to bundle up to 330,000 static rules and dynamically add a further 30,000.

This month, we made the transition even easier for extensions using declarativeNetRequest with the launch of review skipping for safe rule updates. If the only changes are for safe modifications to an extension’s static rule list for declarativeNetRequest, Chrome will approve the update in minutes. Coupled with the launch of version roll back last month, developers now have greater control over how their updates are deployed.

Ecosystem progress

After we addressed the top issues and feature gaps blocking migration last year, we saw an acceleration of extensions migrating successfully to Manifest V3. Over the past year, we’ve even been able to invite some developers – such as Eyeo, the makers of Adblock Plus – and GDE members like Matt Frisbie to share their experiences and insights with the community through guest posts and YouTube videos.

Now, over 85% of actively maintained extensions in the Chrome Web Store are running Manifest V3, and the top content filtering extensions all have Manifest V3 versions available – with options for users of AdBlock, Adblock Plus, uBlock Origin and AdGuard.

What to expect next

Starting on June 3 on the Chrome Beta, Dev and Canary channels, if users still have Manifest V2 extensions installed, some will start to see a warning banner when visiting their extension management page – chrome://extensions – informing them that some (Manifest V2) extensions they have installed will soon no longer be supported. At the same time, extensions with the Featured badge that are still using Manifest V2 will lose their badge.

This will be followed gradually in the coming months by the disabling of those extensions. Users will be directed to the Chrome Web Store, where they will be recommended Manifest V3 alternatives for their disabled extension. For a short time after the extensions are disabled, users will still be able to turn their Manifest V2 extensions back on, but over time, this toggle will go away as well.

Like any big launches, all these changes will begin in pre-stable channel builds of Chrome first – Chrome Beta, Dev, and Canary. The changes will be rolled out over the coming months to Chrome Stable, with the goal of completing the transition by the beginning of next year. Enterprises using the ExtensionManifestV2Availability policy will be exempt from any browser changes until June 2025.

We’ve shared more information about the process in our recent Chrome extensions Google I/O talk. If you have any additional questions, don’t hesitate to reach out via the Chromium extensions mailing list.

Posted by David Li, Product Manager, Chrome Extensions

About a week ago I reported on a case study from Dell and FreeBSD, about Dell’s ThinOS thin client operating system, which basically consists of a proprietary Dell GUI running on top of, at the moment, FreeBSD 12 (they’re moving to FreeBSD 14 for the next ThinOS release). Well, this got me interested – I’ve always been fascinated by thin clients, and a Dell/Wyse FreeBSD ‘distribution’ is just wild enough to be interesting – so I went onto eBay, and bought a Dell thin client. More specifically, I bought a Dell OptiPlex 3000 Thin Client, which comes with an Intel Pentium Silver N6005, a four core CPU without hyperthreading, 16 GB of RAM, a 32GB eMMC storage chip with room for a small M.2 SSD, WiFi 6, Ethernet, USB 3.0, 2.0, and C ports, Bluetooth, and so on. A low-power, but still quite capable little computer that I snagged for a mere €130, which is a steal compared to the full unit price; my configuration is sold new for like €700-800. Of course, these things are sold in batches of hundreds or maybe even thousands of units, and in such volumes corporate clients get massive discounts. Still, it’s a nice deal. My model came installed with Ubuntu 20.04 LTS, which I was not at all interested in. I immediately downloaded the latest ThinOS version for my model, used Dell’s tool and instructions to create a bootable USB, and got to work. The installation process was quick and easy, and does indeed look like an automated FreeBSD installation, TUI and all. After the installation is completed, you get guided through a first-run experience to configure things like the keyboard, WiFi, and so on, and it looks rather fancy. Once I completed the first-run experience, I hit the roadblock I was expecting: in order to use ThinOS, you need a ThinOS Activation License. Since my device was originally sold with (I think) Ubuntu preinstalled, it doesn’t have a TAL in its UEFI, and the only way to push a TAL to a device is to use the Dell Wyse Management Suite. Sadly, the Dell WMS only runs on Windows, and to make matters far worse, only on Windows Server. And it gets even worse – even if I created a Windows Server VM just to run WMS, I need the Pro version, which isn’t free (the free Standard version cannot push TALs), and I’d need to buy a TAL. Aside from the Windows Server restriction, I was aware of these limitations and requirements, so I’m not in the least bit surprised. I was curious to see if buying a TAL was an easy experience, or if it’s entirely geared towards enterprise customers and silly hobbyists like me need not apply. Without a license, I can use the proprietary Dell user interface, but it seems I can’t connect to any possible VDI providers, and I can’t tell what other features might be gated at the moment. With some admittedly very mild poking and prodding, I also haven’t been able to discover any ways of ‘leaving’ Dell’s proprietary GUI to get to a terminal. I’ll do some more prodding over the coming days. I’m not entirely sure where to go from here when it comes to seeing just how much you can do with ThinOS, which was my original goal for this project. I have a feeling the pro version of the Dell Wyse Management Suite is going to be rather expensive – I can’t find any pricing information, which confirms my suspicions – so I think the journey ends here. Unless any OSNews readers have experience with this stuff, and can point me to some tips and tricks to perhaps acquire and install a TAL some other way, there won’t be a more in-depth look at Dell’s weird version of FreeBSD on OSNews. Which sucks, but was to be expected when it comes to enterprise software. Mind you, this does not mean the hardware is going to waste. Not only are there other purpose-built thin client operating systems to experiment with, it is also a full-fledged tiny x86 computer with completely silent passive cooling and a free M.2 slot, so the possibilities are endless.

Pixify’s Reel Maker app to discover the enchantment of storytelling! Create your own romance reels and immerse yourself in a world where love reigns supreme. Allow your imagination to go wild and allow your love story to come to life via beautiful graphics and meaningful words, from treasured memories to private moments. Get the app right away to begin crafting your love story right now!

https://thepixify.com/?utm_source=Seo&utm_medium=videosubmission&utm_campaign=pixify_web_promotions

Milano, 30 mag. (askanews) – Nel percorso verso la sostenibilità, Lidl Italia taglia un nuovo traguardo: l’apertura del punto vendita più green mai realizzato nel nostro Paese, un progetto pilota che vede nell’esperienza italiana un punto di riferimento per l’intero gruppo. Il 30 maggio, infatti, apre le sue porte il nuovo supermercato di Villafranca di Verona, dove l’insegna discount è presente dal 1992 e dove da domani inizierà il nuovo percorso:”È un progetto nato da un’idea del 2018 nata qua in Italia che poi insieme alla nostra casa madre è stato sviluppato – ci ha detto Emilio Arduino, amministratore delegato Servizi Centrali e Sviluppo Immobiliare Lidl Italia – ovviamente io sono molto orgoglioso che sia stata assegnata al Team italiano ma ovviamente rappresenta il primo punto vendita in questo tenore per tutto il mondo Lidl”.Il nuovo punto vendita, che sostituisce quello storico, è stato pensato e realizzato come un negozio completamente autosufficiente dal punto di vista energetico, dove la scelta dei materiali di costruzione è stata fatta in un’ottica di economia circolare, con la struttura portante in legno, proveniente da foreste certificate PEFC, che cambia totalmente il volto dei negozi e al tempo stesso hanno evitato l’utilizzo di 1.650 tonnellate di calcestruzzo.”Stiamo parlando del punto vendita più innovativo di Lidl Italia ma non solo a livello italiano perché questo sarà in collaborazione con la nostra casa madre il punto vendita di riferimento, prototipo a cui tutti i paesi si ispireranno per mettere a terra i loro progetti di ecosostenibilità – ha detto ancora Arduino – Le caratteristiche principali sono dettate dai classici obiettivi che sono di riduzione del consumo energetico, delle dispersioni energetiche e delle emissioni in atmosfera. Ma si aggiunge un quarto elemento di novità legato alla possibilità di riutilizzare i materiali utilizzati per la costruzione alla fine del loro ciclo di vita in altri utilizzi”.Nel punto vendita veronese si è lavorato all’ottimizzazione della catena del freddo, con banchi e vasche frigo, freezer e impianti di climatizzazione alimentari con refrigeranti naturali come la Co2 e il propano e un sistema di porte per ridurre la dispersione del freddo. Anche l’acqua piovana grazie a cisterne di raccolta sotterranee verrà riutilizzata per l’irrigazione del verde con un conseguente risparmio idrico del 65%. Tutte scelte che hanno visto i progettisti impegnati in un meticoloso lavoro di analisi e valutazione: “Il committente ha richiesto un edificio a basso consumo energetico questo ha voluto dire un coordinamento tra la parte impiantistica e l’involucro che è molto prestazionale e impianti che non funzionassero con combustibili fossili – ha raccontato l’architetto Marco Contini – qui gli impianti funzionano con elettricità alimentati dal fotovoltaico”. Il punto vendita grazie a questo impianto da oltre 570mila kilowattora l’anno è in grado di produrre più energia di quanta ne serva, aprendo la strada a un nuovo modo di pensare il retail.

Certainly! Here’s a detailed description of a fictional land cruiser car:

—

### **Toyota Land Cruiser 2024: The Ultimate Off-Road SUV**

#### **Overview**
The 2024 Toyota Land Cruiser continues its legacy as a premier off-road SUV with unparalleled reliability, robust performance, and luxurious comfort. This vehicle is engineered for adventure, capable of tackling the toughest terrains while offering a refined driving experience for everyday use.

#### **Exterior Design**
The 2024 Land Cruiser features a bold and commanding presence, characterized by its:

– **Robust Front Grille**: A striking, large grille with chrome accents that convey strength and elegance.
– **LED Headlights and Fog Lights**: Modern, sleek LED lights provide superior visibility and a distinctive look.
– **Rugged Body Frame**: Reinforced body-on-frame construction ensures durability and off-road capability.
– **All-Terrain Tires and 18-Inch Alloy Wheels**: Durable and stylish, ready for any adventure.
– **Roof Rails and Tow Hooks**: Functional design elements for carrying extra gear and facilitating vehicle recovery in rough conditions.

#### **Interior Comfort and Technology**
The interior of the Land Cruiser is designed with premium materials and cutting-edge technology to ensure comfort and convenience:

– **Spacious Seating for Eight**: Plush leather seats with heating and ventilation options for front and second-row passengers.
– **Advanced Infotainment System**: A 12.3-inch touchscreen with navigation, Apple CarPlay, Android Auto, and a premium JBL audio system.
– **Multi-Zone Climate Control**: Independent climate zones for front and rear passengers.
– **Luxury Features**: Wood and metal trim accents, ambient lighting, and a panoramic sunroof for an upscale feel.
– **Safety and Driver Assistance**: Toyota Safety Sense suite, including adaptive cruise control, lane departure warning, blind-spot monitoring, and a 360-degree camera system.

#### **Performance and Capability**
The 2024 Land Cruiser excels in both performance and off-road prowess:

– **Powerful Engine**: A 3.5-liter V6 twin-turbo engine delivering 409 horsepower and 479 lb-ft of torque.
– **Transmission**: 10-speed automatic transmission providing smooth and responsive shifting.
– **Four-Wheel Drive (4WD)**: Full-time 4WD with a multi-terrain select system for optimized traction on various surfaces.
– **Suspension**: Kinetic Dynamic Suspension System (KDSS) for enhanced stability and comfort on uneven terrains.
– **Towing Capacity**: Capable of towing up to 8,100 pounds, ideal for boats, trailers, and other heavy loads.

#### **Off-Road Features**
Built for the most challenging conditions, the Land Cruiser includes:

– **Crawl Control and Multi-Terrain Monitor**: Helps navigate difficult terrains by automatically adjusting throttle and brakes.
– **Skid Plates and Off-Road Tires**: Protects underbody components and ensures grip on loose surfaces.
– **High Ground Clearance and Water Wading Capability**: A

Iga Swiatek admits she didn’t expect to come back to win after facing match point against Naomi Osaka at the French Open

Back in March I started to look at sponsors for the time I’m spending working on the Drupal core issue queue. It’s
been a few months and I wanted to go back on all the sponsored commits I made as a Frontend Framework Manager, to
show how the sponsorships helped Drupal for the past few months.

The sponsorship offer is simple: you send me a fixed monthly fee of 2500€, and I share the issue credit
of every Drupal core commit that I make. I’m very thankful to Palantir.net and OPTASY
who are sponsoring me. Thanks to them I was able to increase the amount of commits I can make to Drupal core. In the
last 3 months I committed 61 issues (worth 610 weighted issue credits) and the more sponsors I have,
the more time I can spend reviewing and committing issues.

1. Differentiate visually dragging with and without hierarchy A nice improvement for editors working a lot with lists and trees
2. Sticky table header is not sticky if –drupal-displace-offset-top is not defined
3. [jQuery 4] ajax.js and jquery.form.js use deprecated function $.parseJSON() Preparing for the next release of jQuery 4 with some cleanup.
4. cspell check is broken in commit-code-check.sh Sometimes we break the CI and it needs to be fixed 🤷
5. CKEditor admin toolbar config buttons using ::before to add content: have invalid screen reader text It takes dedication to land those accessibility fixes, kudos to our accessibility contributors.
6. Linking in CKEditor 5: URLs with top-level domain but without protocol should get a protocol added automatically
7. #states disable property has stopped working for submit button and other elements Sometimes when we clean-up code, we clean too much and break some other parts of the code
8. Setting width for sticky-header is broken
9. Negotiate max width/height of oEmbed assets more intelligently
10. States API doesn’t work with multiple select fields This was a a 13 years old issue! It _always_ feels good to close an issue that old.
11. Add deprecation/bc support for library-overrides when files are moved Making sure backwards compatibility is working and useful
12. Remove default event from collpased nav-tabs button
13. [DrupalHtmlEngine] HTML-reserved characters (>, <, &) in <script> and <style> tag are converted to HTML entities It happens that we fix things for uses cases that stretch the reasonable (like having whole script tags in a WYSIWYG field)
14. Olivero: Show content preview checkbox is not center aligned with the layout builder buttons. Even a minor issue of a misaligned text by a few pixels is worth fixing
15. Drupal.theme.progressBar() does not escape output correctly
16. filter_autop should ignore twig.config debug html comments Making sure Developer experience doesn’t impact regular users
17. tablePositionSticky should not be called on a non-array variable
18. CKEditor 5 table cell vertical align “middle” doesn’t work
19. Move system/base component CSS to respective libraries where they exist A surprising performance improvement. There are still some low hanging fruits to improve the default frontend performance of Drupal
20. Remove country setting from the installer When you don’t need a piece of data, just don’t collect it
21. Media Library widget display doesn’t return to first page on applying filters
22. Deprecate and remove the AJAX replace method That was a leftover D7 era deprecation
23. Claro should use libraries-extend for views_ui.css Even in core it happens that we don’t use the right way to do something
24. Removal :tabbable usage in dialog.js Some more jQuery 4 preparation
25. Close icon is ovrlapping the title text in modal in claro Yes, typos can make it in the commit log
26. Convert Olivero’s teaser into a single directory component Slowly but surely we’re adding Single directory components to Drupal core
27. Refactor (if feasible) uses of the jQuery animate function to use Vanilla/native More CSS awesomeness making JavaScript code disapear
28. [11.x] Update to jQuery 4.0.x beta Drupal staying on the bleading edge of frontend developement 🙂
29. Refactor some uses of the jQuery parents function to use vanillaJS Did a small post earlier about this, CSS is really very good
30. [regression] Uncaught TypeError: Cannot read properties of null (reading ‘style’) (toolbar.js)
31. JSDoc for ajax command “changed” is incorrect There was a bunch of documentation fixes around this time
32. menu_heading_id variable is not set in menu-region–footer.html.twig
33. Add @file documentation to navigation.html.twig layout template
34. Add @file documentation to menu-region–footer.html.twig template
35. Views UI action buttons create janky layout shift on page load Polishing the loading of pages with heavy JS usage is important to show we care about UX
36. Remove bottom radius on hover state of expanded sub menu item
37. Setting empty URL when making embedded media a link in CKEditor5 causes JS errors
38. Update color of submenu title text
39. Collapsed nav-tabs status not exposed to screen reader There is a good number of accessibility fixes after this one, always nice to commit
40. Incorrect padding on child menu items
41. Claro: Form labels that are disabled have too low color contrast
42. Claro should not hardcode decimal list style type for <ol>
43. Some of string comparisons should use String.prototype.startsWith() or String.prototype.endsWith() Removing regular expressions as much as we can is a noble goal
44. Location of “Skip to Main” link below admin toolbar in Claro is problematic for screen magnifier users
45. Focus states on mobile second level navigation items can get cut off in Olivero
46. Regression: Shortcuts menu flickers when the page is loaded Those toolbar flickering issues are tricky. Thankfully the new navigation module code is simpler than the existing Toolbar code, so it’s much much easier to deal with
47. escapeAdmin.js functionality should be removed(it not used anymore) Removed the feature that removed the overlay… for now, escapeAdmin will be back one way or another)
48. Navigation module offsets the Olivero skip link element
49. Umami page.tpl.php breaks block placeholders Sometime themes can break really nice Drupal features (like bigpipe)
50. Claro CSS for dropbutton items adds large gap of white space
51. Replace dialogContentResize jQuery event with CustomEvent Those events issues are really exciting, we’re moving away slowly from jQuery for event management
52. Umami views should use responsive grid Another case of core not using the awesome features we provide, not anymore 🙂
53. Claro highlighted row not communicated to keyboard users
54. Fix overflow visibility for wrapper content in navigation CSS
55. Claro details component does not have the right class
56. Make drupal.tableheader only use CSS for sticky table headers I will always welcome CSS-removing-JS patches
57. Mismatch between implementation and description for Drupal.Message.prototype.remove().
58. “Skip to main content” link skips over content that is essential to the page, banner role should be for global content
59. Add pdureau as a co-maintainer for the Theme API with a focus on SDC Adding new maintainers is too rare. In this case the community is better for having him around
60. Choose an icon for the Announcements link
61. Remove deprecated moved_files entries in core

Many of these issues are maintenance focused, it’s not shiny, it’s not exciting, and it needs to be done.
Sponsoring big initiatives like Starshot is exciting, let’s not forget the unexciting day to day that keeps things
running. If you’re interested in supporting my work on Drupal core and keep the frontend fixes coming,
consider sponsoring me.