Make WordPress Core

Change History (4)

#1 @khushipatel15
3 weeks ago

function adjust_reading_time_based_on_browser( $time, $words ) {

$user_agent = $_SERVERHTTP_USER_AGENT?;


if ( strpos( $user_agent, 'Firefox' ) !== false ) {

$time = $words / 200; Adjust the time calculation for Firefox

}


return $time;

}
add_filter( 'reading_time', 'adjust_reading_time_based_on_browser', 10, 2 );
Integrate this code snippet in a suitable location within wp-includes/formatting.php.

#2 @poena
3 weeks ago

  • Component changed from Administration to Editor
  • Keywords close added
  • Severity changed from critical to normal

Hi @federico1447 and welcome to WordPress Trac!

Bugs and feature requests for the block editor and the blocks are managed in the Gutenberg GitHub repository (There is a notice about this before you create your Trac ticket). Changes are made in Gutenberg and then tested in the plugin before they are added to WordPress.

Please open a new issue in the GitHub repository, and include all steps that are needed to reproduce the problem.

Here is a list of reported issues for the Time to read block: https://github.com/WordPress/gutenberg/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%5BBlock%5D%20Time%20to%20Read%22

Once that is done, this ticket should be closed as "reported upstream"

This ticket was mentioned in Slack in #accessibility by joedolson. View the logs.


2 weeks ago

#4 @joedolson
2 weeks ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

At the most, this might be something that would be done via a filter. However, the Time To Read block has not yet been added to core; the comments you're linking to are specific to WordPress.com, so any issues you have with that block should be raised at WordPress.com, where they may be using a custom block.

Note: See TracTickets for help on using tickets.