Make WordPress Core

#57668 closed defect (bug) (reported-upstream)

Query Loop Top Border Issue

Reported by: hiren1094's profile hiren1094 Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: General Keywords: has-screenshots dev-feedback
Focuses: ui, css Cc:

Description

Hello,

Top border should be show on mouse hover When I select the query loop block

Attachments (2)

Query_loop.png (313.3 KB) - added by hiren1094 16 months ago.
Query Loop UI
Query_loop-6.1.png (33.5 KB) - added by hiren1094 15 months ago.
Query Loop 6.1

Download all attachments as: .zip

Change History (13)

@hiren1094
16 months ago

Query Loop UI

#1 in reply to: ↑ description @hiren1094
16 months ago

Replying to hiren1094:

Hello,

Top border should be show on mouse hover When I select the query loop block

I have checked in "6.2-beta1"

#2 @hiren1094
16 months ago

  • Version trunk deleted

#3 @costdev
15 months ago

  • Keywords reporter-feedback added

Hi @hiren1094, does this issue exist in WordPress 6.1?

#4 @hiren1094
15 months ago

@costdev

The layout totally different compared to 6.1.

Please check above file attached for 6.1.

@hiren1094
15 months ago

Query Loop 6.1

#5 @costdev
15 months ago

Thanks @hiren1094! I'll add this to the 6.2 milestone for visibility.

Could you check the issues on the Gutenberg repository and if it hasn't already been reported, open a new issue and drop a link to it in here?

#6 @hiren1094
15 months ago

@costdev

I have raised issue on gutenberg repository.

And here the link of issue https://github.com/WordPress/gutenberg/issues/47909

#7 @costdev
15 months ago

  • Keywords reporter-feedback removed

Thanks @hiren1094!

@audrasjb Do you want to keep this ticket open and milestone for 6.2 to track this issue, or close this as reported-upstream and wait until folks on the Gutenberg repo know if this is handled/will be handled for 6.2?

#8 @costdev
15 months ago

  • Keywords dev-feedback added

#9 @audrasjb
15 months ago

For now, let's keep this ticket open to track the related issue. But not sure it's something that will be fixed in 6.2. If not, we can move the ticket to 6.3 :)

#10 @audrasjb
15 months ago

  • Milestone changed from Awaiting Review to 6.2

#11 @audrasjb
15 months ago

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

Well, I changed my mind. Let's close this as reported-upstream. I didn't notice that the ticket wasn't milestoned to 6.2 yet :)

Note: See TracTickets for help on using tickets.