Basically I am seeing #748570: Subject line in comment form is too long with both sidebars just with AT (Corolla subtheme).
The subject line is way too long in portrait mode on a mobile device and depending on the mobile browser wrecks some havoc with the overall design (Opera mobile yuck, on Dolphin the line just "leaves" the themed area).

I wonder if this is something AT can handle or if this is due to Drupal core behavior.

Comments

dddave’s picture

Title: Comment subject line woes » Subject line in comment form too long on mobile devices
Jeff Burnz’s picture

Please link directly to a comment or node with comments that show this.

dddave’s picture

http://fromwaydowntown.de/content/paris-revisited

This happens on any piece of content with comments enabled. Confirmed on Dolphin, Opera mobile and mini and the default Android browser on my Galaxy 2S.

Jeff Burnz’s picture

Title: Subject line in comment form too long on mobile devices » Subject form input in comment form too long on mobile devices

Oh right, are you talking about the form input, the actual form item? Right, I see now, I thought you mean the actual comment subject as printed on the comment...

input.form-text  {
  max-width: 100%;
}

... should solve this across the board, but I seem to have some memory of there being issues with this and a reason why I don't do this by default, will need to refresh my memory, can you test with that on Corolla.

The other fix is less attractive IMO, using a form alter to reduce "size" in the markup, although that would allow us to make it the same width at the name, email, homepage inputs, could look attractive? Hmmm.

dddave’s picture

Quick check suggests that this works.

Jeff Burnz’s picture

Status: Active » Fixed

OK, I'm running with this, I've asked around the traps and lots of people are doing either this or using width:100% which frankly I rapidly dislike.

I will put this into all styled themes (its in, just need committing). Actually it was already in the core theme, I just tweaked it a little, it was applying to input which I think is too dangerous and untested in the new input types in HTML5, so have restricted it back to just input.form-text.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.