[FM Discuss] css question
tar.gz
tar.gz at 1904.cc
Fri Jun 25 04:22:07 PDT 2010
actually this case goes beyond the simple matter of CSS adjustment. the
question is rather how the interface should deal with images that are
bigger than the text frame.
should the images be forced to stay at the text-frame's size?
then we could do this :
.content-container img {max-width:100%;}
or should the container window adapt to images of any size?
that would be the code that Martin proposes below. but if somebody
uploads a 2000px-wide image, the text frame will become incovenient to read.
the smartest solution would be that for large images, the server
generates a smaller image with a maximal width of 600 or 700px,
conforming to the default text frame width. and *if* the original image
is bigger, the system could generate a Lightbox-type zooming button.
that feature would be important also to ensure a smaller pageload, hence
accessibility.
Martin, let me know if you need any help with the html.
best,
Manuel
adam said the following on 6/25/10 12:52 AM:
> thanks!
>
> if u can help me replace all tables with divs then please feel
> free... :)
>
> adam
>
>
>
> On Fri, 2010-06-25 at 10:38 +1200, Martin Kean wrote:
>> Hi,
>>
>> The quick fix is :
>>
>> .content-container {min-width: 700px;}
>>
>> works in FF, IE, Chrome, Opera (not sure about Safari).
>>
>> I have added it into booki.css (attached).
>>
>> But really booki should be progressive and standards compliant and do away with tables in favour of DIVs (even fluid Divs!)
>>
>> cheers, Martin
>> ________________________________________
>> From: discuss-bounces at lists.flossmanuals.net [discuss-bounces at lists.flossmanuals.net] On Behalf Of adam hyde [adam at flossmanuals.net]
>> Sent: Thursday, 24 June 2010 10:36 p.m.
>> To: discuss at lists.flossmanuals.net
>> Subject: [FM Discuss] css question
>>
>> hi
>>
>> can someone tell me a quick fix so that booki pages resize to show the
>> content nicely ie:
>>
>>
>> http://www.booki.cc/micro-turf/turf-8-canalpotsdamer-platz/
>>
>> adam
>>
>>
More information about the Discuss
mailing list