Tag: chrome

  • Chrome Canary Adds Flag for Disabling FLoC Testing

    Chrome Canary Adds Flag for Disabling FLoC Testing

    Google’s controversial Federated Learning of Cohorts (FLoC) experiment now has a feature flag within Chrome Canary (the nightly build of Chrome for developers) that allows users to opt out. In January 2020, Google announced its plans to discontinue support for third-party cookies in Chrome within two years. The first bits and pieces of the company’s…

  • Joomla Blocks FLoC by Default, Drupal Moves to Block FLoC in Upcoming 9.2 Release

    Joomla Blocks FLoC by Default, Drupal Moves to Block FLoC in Upcoming 9.2 Release

    Joomla has announced plans to block Google’s Federated Learning of Cohorts (FLoC) by default going forward. The 3.9.2.7 security update, released yesterday, added a Permissions Policy header to disable FLoC. Users can now find a new setting in Global configuration on the Site tab in the Site Settings area, where they can toggle FLoC on…

  • FLoC Blocking Discussion Continues on WordPress Trac

    FLoC Blocking Discussion Continues on WordPress Trac

    Last week WordPress contributors began a heated discussion regarding blocking FLoC (Federated Learning of Cohorts). Google’s experimental alternative to third-party cookies has become a highly contentious topic that made its way into last week’s Core developers meeting. Representatives from the Chrome team also attended the meeting to clear up any confusion and answer questions about…

  • WordPress Contributors Propose Blocking FLoC in Core

    WordPress Contributors Propose Blocking FLoC in Core

    WordPress contributors are proposing the project take an active position on Google’s Federated Learning of Cohorts (FLoC). This particular mechanism is Google’s alternative to third-party cookies that doesn’t require collecting users’ browsing history. The GitHub repository for FLoC explains how Google will group people together and label them using machine learning: We plan to explore…

  • Chrome 90 to Use HTTPS by Default in the Address Bar

    Chrome 90 to Use HTTPS by Default in the Address Bar

    Chrome’s upcoming version 90 will use https:// by default in the address bar, bringing a significant improvement to security and loading speed. HTTPS adoption has shot up significantly over the past six years after Google announced in 2014 that HTTPS would be used as a ranking signal in search results. In February 2021, W3Techs found that 82.2% of websites…

  • Chrome is Testing a Follow Button for Websites

    Chrome is Testing a Follow Button for Websites

    Chrome Canary, the browser’s nightly build for developers, has been testing a new Follow button, as spotted on Android by the publishers of Chrome Story. The button appears on the homepage of a site, as well as in the browser menu: Chrome Story speculates that it may be integrated with Google’s Discover feature, allowing sites…

  • Google Chrome Announces Rollout Plan for Blocking Mixed Content Beginning January 2020

    Google Chrome Announces Rollout Plan for Blocking Mixed Content Beginning January 2020

    The Google Security Team has announced a timeline for when Chrome will begin blocking mixed content by default in order to ensure that HTTPS browsing is more secure. Mixed content refers to HTTPS pages that load resources, such as images, videos, stylesheets, and scripts, over HTTP. The gradual rollout will begin with Chrome 79, which…

  • WPWeekly Episode 324 – Getting NC State Gutenready

    WPWeekly Episode 324 – Getting NC State Gutenready

    In this episode, John James Jacoby and I are joined by Jen McFarland, Web Services Coordinator at NC state’s Office of Information and Technology. McFarland describes how the campus is using WordPress, what they’re doing to prepare students and staff for Gutenberg, and what they’ve experienced thus far in the transition. Near the end of…

  • Google Chrome Rolls Out “Not Secure” Warning for Plain HTTP Sites

    Google Chrome Rolls Out “Not Secure” Warning for Plain HTTP Sites

    As part of a long term plan to push the web to adopt HTTPS encryption, Google Chrome is now marking all plain HTTP sites as “not secure,” as of July 24, 2018, with the release of Chrome 68. Previously, the “not secure” warning was hidden behind the security indicator in the URL bar as shown…

  • Google Chrome v62 Adds Support for OpenType Variable Fonts, Expands HTTP Warnings

    Google Chrome v62 Adds Support for OpenType Variable Fonts, Expands HTTP Warnings

    Google Chrome version 62 was pushed to the stable channel for Windows, Mac, and Linux today and will be rolling out to users over the next few days. The browser is continuing to put the pressure on website owners to migrate to HTTPS. As expected from the roadmap laid out earlier this year, a “Not…

  • WordPress 4.7.4 Fixes 47 Issues

    WordPress 4.7.4 Fixes 47 Issues

    WordPress 4.7.4 is available and is a maintenance release that fixes 47 issues reported against 4.7. This update includes a visual editor compatibility fix for an upcoming version of Chrome. Uploading video and audio files no longer result in broken thumbnails and the REST API received a few enhancements related to data handling. WordPress 4.7.4 also restores the ability to…

  • Chrome to Add Security Warning to HTTP Sites Beginning 2017

    Chrome to Add Security Warning to HTTP Sites Beginning 2017

    The Google Chrome Security team announced yesterday the browser will begin labeling HTTP connections as insecure starting in January 2017. Chrome currently displays a green lock icon in the address bar for sites that are secure but the security team will be taking it one step further by displaying a warning on unencrypted sites. “Beginning…