I think it's worth noting that there is a lot of commonality between
accessibility and mobile optimisation. When the W3C Mobile Web Best
Practices Group began its work (way back in June 2005 - I'm feeling old)
our starting point was WCAG. They're not the same, of course, but the
ways of
Hi Grant,
You could have a dedicated mobile site (using a sub-domain and server-side
client detection, for instance) with zero regard paid to accessibility
*or*standards.
Responsive design (using media queries, for instance) follow the DRY
principle - Don't Repeat Yourself. Rather than think
http://ricochet.org/new_floradise/arrangements.html
http://ricochet.org/new_floradise/plants.html
hey all,
i'm having trouble positioning a background image. on the arrangements page,
the two arrows have a blue border.
the first problem i'm having is that bbedit, safari, firefox and opera (on
simple
you must put something like this:
border:none
for example
if image is link, then:
*
*
*a img {border: none; }*
or:
*a:link {border:none}*
*
*
*I hope this could be helpful. Try!*
*
*
On Wed, May 16, 2012 at 7:00 PM, ron zisman ronzis...@mac.com wrote:
On May 16, 2012, at 1:32 PM, Mladen Barac wrote:
simple
you must put something like this:
border:none
for example
if image is link, then:
a img {border: none; }
or:
a:link {border:none}
I hope this could be helpful. Try!
thank you mladen. i put the border on to better see
the first problem i'm having is that bbedit, safari, firefox and opera (on
a mac) all position it in a different location (#pre-nex).
Hi,
Try 'position: relative' for #main (the containing div of #pre_nex).
Best regards,
Kepler Gelotte
Neighbor Webmaster, Inc.
156 Normandy Dr., Piscataway,
We have a feature in our CMS that allows users to add a spotlight box of
related content to the right of the main content. This is not a right column
(which we also allow) but a floated block of content. Visually this works well
and the user base wants the feature. Unfortunately, there are
On May 16, 2012, at 2:11 PM, Kepler Gelotte wrote:
the first problem i'm having is that bbedit, safari, firefox and opera (on
a mac) all position it in a different location (#pre-nex).
Hi,
Try 'position: relative' for #main (the containing div of #pre_nex).
Best regards,
mercy,
On 17/05/2012, at 4:23 AM, Rick Hill wrote:
The ideal would be to position the related content at the bottom of the
associate main content and then position it at the top right of the main
content. So visually it would look the same but the HTML reading order and
header nesting would be
Hi, Grant,
I'd recommend you have a look at this: http://cssgrid.net/
Do it once, do it well, make it flexible. :-)
V.
On 16 May 2012 22:48, wsg@webstandardsgroup.org wrote:
*
WEB STANDARDS GROUP MAIL LIST DIGEST
10 matches
Mail list logo
