Skip to:
Content

BuddyPress.org

Opened 6 years ago

Closed 6 years ago

Last modified 23 months ago

#7956 closed defect (bug) (wontfix)

Customizer - While accessing the activity page form customizer, It shows NOT ALLOWED CURSOR on Hover Event of Post button.

Reported by: krupajnanda's profile krupajnanda Owned by:
Milestone: Priority: normal
Severity: minor Version:
Component: Core Keywords: needs-patch ux-feedback has-screenshots
Cc:

Description

Please check the steps as mentioned below.

  1. Open the Activity page in Customizer
  2. Add the content in #whats-new-textarea Text area
  3. Now Hover over the Post Update button
  4. It shows the point arrow like it won't allow to post the content. This is valid in case of empty content but when there is content in text area, it must not such arrow.
  5. It adds css property cursor:not-allowed !important
  6. And after clicking on button, it allows to post the content!

This has been tested with default themes - 2015, 2016 an 2017

Attachments (2)

BP_Nouveau_Activity_Cursor.jpg (180.1 KB) - added by krupajnanda 6 years ago.
Please check this attachment.
Activity in customizer .gif (358.9 KB) - added by krupajnanda 6 years ago.
Please check this visual for more detail for hover event on POST UPDATE button.

Download all attachments as: .zip

Change History (4)

@krupajnanda
6 years ago

Please check this attachment.

@krupajnanda
6 years ago

Please check this visual for more detail for hover event on POST UPDATE button.

#1 @imath
6 years ago

Hi @krupajnanda

Thanks for your feedback. The cursor you're seeing is a Customizer feature. If you preview a single post, you'll see that it also happens for the the Post comment button.

I think the right behavior should be that posting/commenting activities within the customizer shouldn't be available. The customizer is use to customize the Website, not to use it imho.

#2 @DJPaul
6 years ago

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

I think this is sufficiently edge-case and unexpected use of the Customizer, that we don't need to worry about fixing.

Note: See TracTickets for help on using tickets.