Make WordPress Core

Opened 9 months ago

Last modified 7 months ago

#59537 assigned defect (bug)

Quote toolbar is not shown for mobile view

Reported by: oksankaa's profile oksankaa Owned by:
Milestone: Priority: normal
Severity: minor Version: 6.4
Component: Editor Keywords: reporter-feedback
Focuses: Cc:

Description

  1. Create a post
  2. Add a quote
  3. Check that the capture toolbar in the quote block is shown
  4. Change screen size (ex. 768X1024)
  5. Quote toolbar is not shown

Attachments (3)

expected result.png (28.2 KB) - added by oksankaa 9 months ago.
expected result.2.png (28.2 KB) - added by oksankaa 9 months ago.
Actual result.png (63.0 KB) - added by oksankaa 9 months ago.

Download all attachments as: .zip

Change History (11)

This ticket was mentioned in Slack in #core-test by hardikgohil. View the logs.


9 months ago

#2 @oglekler
8 months ago

  • Component changed from Toolbar to Editor

I assume this component should be the Editor. Toolbar component is about the WordPress toolbar.

#3 @hellofromTonya
8 months ago

  • Keywords reporter-feedback added

Hello @oksankaa,

Welcome back to WordPress Core's Trac :) Thank you for reporting this issue.

I am able to reproduce your findings. I'm wondering if this is by design.

The discussion, investigation, and possible fix needs to happen in the Gutenberg repository.
Can you please report this issue upstream in Gutenberg? https://github.com/WordPress/gutenberg/issues

Once reported, can you please comment with a link to the issue, i.e. comment to this Trac ticket? Then this Trac ticket can be closed as reported-upstream.

Why report in Gutenberg?
WordPress Core consumes (uses) the released npm packages that include the editor and its toolbar and tools. Those npm packages (and thus toolbar and tools) are maintained by Gutenberg, not Core.

How do the changes get into Core?
Once fixed and the npm packages released, then Core's package.json is updated, bringing in the latest packages.

#4 @oksankaa
8 months ago

  • Resolution set to reported-upstream
  • Status changed from new to closed

Hello @hellofromTonya,
Thank you for providing the feedback.

I've created a GH issue: https://github.com/WordPress/gutenberg/issues/55709

#5 @hellofromTonya
8 months ago

  • Milestone Awaiting Review deleted

@oksankaa amazing! Thank you :)

#6 @flixos90
7 months ago

  • Owner set to flixos90
  • Resolution changed from reported-upstream to fixed

In 57153:

Themes: Avoid autoloading the previous theme's theme mods when switching to another theme.

This reduces unnecessarily autoloaded data from inactive themes, which can contribute to slow database performance as part of excessive autoloading.

Props mukesh27, rajinsharwar, igmoweb, joemcgill, swissspidy, westonruter, flixos90.
Fixes #59537.
See #59975.

#7 @flixos90
7 months ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Yikes. Wrong ticket reference in my commit message 🤦‍♂️

#8 @flixos90
7 months ago

  • Owner flixos90 deleted
  • Status changed from reopened to assigned
Note: See TracTickets for help on using tickets.