Making WordPress.org

Opened 15 months ago

Closed 2 months ago

Last modified 2 months ago

#6833 closed defect (bug) ( fixed )

Long un-breakable text in support forum reply moves the submit button

Reported by:  sterndata's profile sterndata Owned by:  coffee2code's profile coffee2code
Milestone: Priority: normal
Component: Support Forums Keywords:
Cc:

Description

Per https://wordpress.org/support/topic/long-links-in-support-forum-move-the-submit-button ,


This isn’t actually an issue with WordPress but rather this support forum. I’m working on a desktop computer in Chrome, and if I type a long string of characters (e.g., a long web address) into the “Your message” field when creating a reply to somebody’s post, the input box grows to the right, and the blue “Submit” button moves to the right. When replying to somebody’s message in the forum, this can potentially lead to the “Submit” button appearing under something else making it unclickable.


I've verified this. https://i.imgur.com/LjcfPO0.png

Attachments (2)

image.png ( 121.6 KB ) - added by NekoJonez 10 months ago .
View when editing a message with a long link.
image (1).png ( 231.3 KB ) - added by NekoJonez 10 months ago .
View as trying to post a post with a long link to a topic.

Download all attachments as: .zip

Change History (11)

This ticket was mentioned in Slack in #forums by sterndata. View the logs .


10 months ago

#2 @ NekoJonez
10 months ago

Today, I wanted to warn a dev about a translation mistake and I experienced this issue. I'm going to add my screenshots to have more visual material to troubleshoot.

@ NekoJonez
10 months ago

View when editing a message with a long link.

@ NekoJonez
10 months ago

View as trying to post a post with a long link to a topic.

#3 @ NekoJonez
10 months ago

I have been playing around trying to fix this by a simple CSS fix... But, it's going over my head. From the link that Sterndata posted, I tested things. This is the underlying HTML. https://ibb.co/5Wg3HT1

When I edit the fieldset tag CSS, I can move the whole thing but it doesn't accept a max-width CSS rule.
When I add 'max-width: 73%' to #bbpress-forums div.bbp-the-content-wrapper, the editor doesn't overlap anymore BUT, the submit button doesn't move at the right location.
I think it's that one div without any class that's being the issue here... Since, if that one has a class, this issue can be easily fixed in CSS. Since, if you now use that CSS fix I said earlier, the whole page looks strange.

Anyways, that's how I see it... I'm curious if I'm close to the actual solution or issue... Since, I'm trying to learn CSS/HTML & PHP more.

This ticket was mentioned in Slack in #meta by nekojonez. View the logs .


10 months ago

#5 @ bcworkz
10 months ago

Some more info about this: This is unique to the forum's block editor. (blocks everywhere plugin I think). It does not happen with the "classic" editor. Thus a crude workaround until this is resolved would be to temporarily disable the block editor in one's forum profile.

#6 @ Presskopp
10 months ago

This could be fixed by applying a width plus either word-wrap: break-word or overflow-wrap: break-word - but there also are breakpoints to be considered:

 .editor-styles-wrapper.block-editor-writing-flow { word-wrap: break-word; /* overflow-wrap: break-word; */ width: 34rem; } < 961px width: 28rem; < 821px width: 27rem;

#7 @ coffee2code
2 months ago

  • Owner set to coffee2code
  • Resolution set to fixed
  • Status changed from new to closed

In thirteen thousand three hundred and eighty-five :

Support: Prevent long unbroken text from expanding topic/reply input beyond its container.

Props sterndata, nekojonez, bcworkz, presskoop, coffee2code.
Fixes #6833 .

#8 @ coffee2code
2 months ago

In thirteen thousand three hundred and ninety-three :

Support: Fix improper word wrapping behavior for topic/reply input.

Props macmanx, foosantos.
See #6833 .

#9 @ sterndata
2 months ago

seems a bit hacky... If I type a long line, breaks occur at the width of the box, not at work breaks. But, at least, I can still find the submit button. :-)

Note: See TracTickets for help on using tickets.