WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 18 months ago

#16954 closed enhancement (invalid)

Set "min-width" for textareas

Reported by: Simek Owned by:
Milestone: Priority: normal
Severity: trivial Version: 3.1
Component: UI Keywords: has-patch reporter-feedback
Focuses: Cc:

Description

Even we've set "resize: none;" for all textareas sometimes browser ignores it and allow user to resize those fields.

To prevent resizing it to the smallest size when can set "min-width" for every element which has width defined.

Attachments (1)

minwidth.patch (2.7 KB) - added by Simek 3 years ago.

Download all attachments as: .zip

Change History (12)

Simek3 years ago

comment:1 Simek3 years ago

Webkit based browsers default don't allow to shrink width and height of textareas.
Patch works properly for Gecko based browsers.

comment:2 follow-up: scribu3 years ago

  • Keywords reporter-feedback close added

If you set resize: none, why not also add the CSS you wrote in the patch?

comment:3 in reply to: ↑ 2 Simek3 years ago

Replying to scribu:

If you set resize: none, why not also add the CSS you wrote in the patch?

I'm not sure that I understood you, but this patch is prepared to be applied and fixes shrinking issue for browsers which ignores resize: none.

comment:4 toscho3 years ago

  • Cc info@… added

Why is resizing to a smaller size a problem? Users may do that to make the textarea fit into a small window.

comment:5 follow-up: scribu3 years ago

Ah, I see that resize: none is actually done in wp-admin.css not a plugin.

toscho asked a good question.

comment:6 follow-up: Simek3 years ago

Remember that normal text inputs are not resizeable, so even the user resize textarea to fit small resolution, the rest of inputs will remain with standard width and cause vertical scroll.

According to resize:none in wp-admin.css - FF 4 (Gecko based) ignore this setting completely, Safari and Chrome (Webkit based) ignores this setting partial (don't allow to shrink areas but allow to resize).

I made some test with this and I must say that "none" value is a problem because when I set resize to "horizontal" all browsers interpreted it in a good way.

comment:7 scribu3 years ago

Remember that normal text inputs are not resizeable, so even the user resize textarea to fit small resolution, the rest of inputs will remain with standard width and cause vertical scroll.

How would a fixed width cause vertical scroll? You mean horizontal scroll, right?

I made some test with this and I must say that "none" value is a problem because when I set resize to "horizontal" all browsers interpreted it in a good way.

Again, shouldn't you be testing "resize: vertical"?

comment:8 Simek3 years ago

You've got right - there should be horizontal scroll mentioned in first paragraph and vertical value for CSS "reset" attribute.

comment:9 in reply to: ↑ 6 toscho3 years ago

Replying to Simek:

Remember that normal text inputs are not resizeable, so even the user resize textarea to fit small resolution, the rest of inputs will remain with standard width and cause vertical scroll.

Yes, but these controls are accessibe by tabbing and they fit usually on a single page. But writing in a textarea that is wider than the page is a pain. I’m asking for the user’s benefits of such a restriction to understand the issue.

comment:10 in reply to: ↑ 5 ocean9020 months ago

Replying to scribu:

Ah, I see that resize: none is actually done in wp-admin.css not a plugin.


Replying to Simek:

Even we've set "resize: none;" for all textareas sometimes browser ignores it and allow user to resize those fields.

In wp-admin.dev.css I could only find one resize: none, for #replycontent: http://core.trac.wordpress.org/browser/tags/3.1/wp-admin/css/wp-admin.dev.css#L3511

global.dev.css doesn't contain such a declaration too.

So, what is the issue and does it still exists?

comment:11 helenyhou18 months ago

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

Looks like resize: none does not exist anywhere except for the distraction free/fullscreen editor and media views (3.5 trunk), both of which are specific, so I'm going to guess this isn't an issue anymore. Feel free to reopen if this isn't the case.

Note: See TracTickets for help on using tickets.