Closed (fixed)
Project:
AdaptiveTheme
Version:
7.x-3.x-dev
Component:
CSS/HTML
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 May 2012 at 16:16 UTC
Updated:
28 May 2012 at 08:20 UTC
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
Comment #1
dddave commentedLink to site: www.fromwaydowntown.de
Comment #2
Jeff Burnz commentedPlease link directly to a comment or node with comments that show this.
Comment #3
dddave commentedhttp://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.
Comment #4
Jeff Burnz commentedOh 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...
... 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.
Comment #5
dddave commentedQuick check suggests that this works.
Comment #6
Jeff Burnz commentedOK, 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.