As far as I know there are no different versions for 32 and 64 bit, this must
have something to do with your own computer. Adobe has a first line and second
line helpdesk, they should be able to assist you with this.
Working with the semantical HTML5 elements I keep feeling aversion to the extra
elements I am producing. Like the nav element, using it as a container for a
menu in an list does not feel as an advantage, I never needed a container for
the list before. I trained myself in keeping the code
profile - but those aren't navigation links. The nav
/ element tells search engines etc. what this list of links is for.
Dunno if that makes sense,
On 22/11/2011 14:32, Frances de Waal wrote:
Working with the semantical HTML5 elements I keep feeling aversion to the
Thank you, David, good to know, I am afraid this is an example of what made me
pose this question :). Suppose time will solve it all!
Op 22 nov 2011, om 16:52 heeft David Hucklesby het volgende geschreven:
On 11/22/11 6:32 AM, Frances de Waal wrote:
Zelfstudiehandboek Websites Ontwikkelen met HTML, CSS en Dreamweaver
WaalWeb | Halfweg, Noord-Holland | KvK 34350833
Op 27 sep 2011, om 23:33 heeft Hassan Schroeder het volgende geschreven:
On 9/27/11 1:42 PM, Frances de Waal wrote:
As far as I know all
You can have multiple semanticle HTML5 elements like header, article, section,
, footer, aside and nav elements in one webpage. It all depends on it if you
want to give the content a semantical meaning, if so, use the corresponding new
elements. Only if the box is for other purposes
As far as I know all the stylesheets ánd all the linked resources in them like
background-images will be loaded with meadia-queries. So I am afraid that the
large background image that you try to avoid for mobiles, will be loaded anyway
as long as you try to solve this with
blank cause of one little mistake in the code. Removing the content-
type meta-tag makes Dreamweaver to convert the page to ISO instead of
UTF, maybe other editors do so as well. Our experience with
application/xhtml+xml in a nutshell is that the web is not set for it.
, each line
having a line break.
[mailto:li...@webstandardsgroup.org] On Behalf Of Frances de Waal
Sent: Sunday, December 06, 2009 3:42 PM
Subject: [WSG] breaks, lists in a form or not, and more or less divs
clean. I was just focused on InContextEditing but of course
many other CMS's need just as well more divs, I realised after.
Thanks for your reply!
Frances de Waal
List Guidelines: http://webstandardsgroup.org/mail
about 100 divs here. So, besides of best practice, is there any place
where the extra divs may have bad influence?
Frances de Waal
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Mail list logo