What are the main differences between XHTML Strict and Transitional?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Strict removes the Target attribute from links, not sure what else. Aha! DuckDuckGo is my friend: http://www.zvon.org/xxl/xhtmlReference/Output/comparison.html
Walter
On Sep 26, 2012, at 10:26 AM, RavenManiac wrote:
What are the main differences between XHTML Strict and Transitional?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
So, what happens if you use a forbidden attribute? How will you be notified?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
You will see the page not validate at the W3C validator, and not much else.
The benefit to creating a valid page is that you remove ambiguity from what you send to to the browser. Meaning, if the browser screws it up, that’s on them, not you.
This is particularly important when you start messing with the page using JavaScript: if you start with a valid page, you remove a layer of possible errors immediately. JavaScript is FAR less forgiving than browsers. Browsers are pretty capable of sorting out the most glaring of errors and showing something on the screen.
Walter
On Sep 26, 2012, at 10:38 AM, RavenManiac wrote:
So, what happens if you use a forbidden attribute? How will you be notified?
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Okay, I’ve been having fun with XHTML Strict tonight. 
For the most part, all of my regular FWP pages transitioned from HTML 4.01 Transitional to XHTML 1.0 Strict pretty well.
However, I’m definitely having issues with Perch enabled pages. Here’s one of the errors I’m getting a lot:
Line 4, Column 68: document type does not allow element “meta” here; assuming missing “head” start-tag
It sounds like this error has something to do with where I’m placing the Perch code in the HTML Markup using Crowbar. Currently, the code is in Before , but it sounds like it needs to be someplace else. Here’s the specific Perch code:
I’m also having problems with tables. Specifically cell height. All kinds of weird table formatting issues. I ended up going back to HTML 4.01 Traditional until I find out what’s going on.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
I’m also getting errors with Carousel text tabs.
Line 337, Column 270: ID “text_tab_buried” already defined
…=“#buried” style=“cursor:pointer” id=“text_tab_buried”>Buried | <a href="#…
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Yes, this code must go inside the head, so choose either After or Before from the HTML Markup dialog.
Walter
On Sep 27, 2012, at 12:49 AM, RavenManiac wrote:
Okay, I’ve been having fun with XHTML Strict tonight.
However, I’m definitely having issues with Perch enabled pages. Here’s one of the errors I’m getting a lot:
Line 4, Column 68: document type does not allow element “meta” here; assuming missing “head” start-tagIt sounds like this error has something to do with where I’m placing the Perch code in the HTML Markup using Crowbar. Currently, the code is in Before , but it sounds like it needs to be someplace else. Here’s the specific Perch code:
I’m also having problems with tables. Specifically cell height. All kinds of weird table formatting issues. I ended up going back to HTML 4.01 Traditional until I find out what’s going on.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
You likely have more than one tab set to link to the “buried” pane. That’s what this error says – IDs have to be unique in the page.
Walter
On Sep 27, 2012, at 12:56 AM, RavenManiac wrote:
I’m also getting errors with Carousel text tabs.
Line 337, Column 270: ID “text_tab_buried” already defined
…=“#buried” style=“cursor:pointer” id=“text_tab_buried”>Buried | <a href="#…
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
On 27 Sep 2012, 5:04 am, waltd wrote:
You likely have more than one tab set to link to the “buried” pane. That’s what this error says – IDs have to be unique in the page.
Walter
All of my tabs do have unique names, like tab2a, tab2b, tab2c, etc. However, the text in those tabs is the same (i.e. Traditional, Jewish, Value), which they kinda have to be. Please see here: http://www.williamsburgmemorialpark.com/properties/burial.html
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Is there more than one tab pointed at the same pane of the carousel?
Walter
On Sep 27, 2012, at 1:44 AM, RavenManiac wrote:
On 27 Sep 2012, 5:04 am, waltd wrote:
You likely have more than one tab set to link to the “buried” pane. That’s what this error says – IDs have to be unique in the page.
Walter
All of my tabs do have unique names, like tab2a, tab2b, tab2c, etc. However, the text in those tabs is the same (i.e. Traditional, Jewish, Value), which they kinda have to be. Please see here: http://www.williamsburgmemorialpark.com/properties/burial.html
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
Yes, but every tab has a unique identifier.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
The identifier is being set by the Action to match the name of the carousel and the name of the pane, joined with a _. This is my doing, and the only way to get away from it is to only have one text tab per pane for the time being. I can fix this, but it will be a patch to the Action.
Walter
On Sep 27, 2012, at 10:36 AM, RavenManiac wrote:
Yes, but every tab has a unique identifier.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
No worries Walter. I can wait for the next update to the action. Thanks for your help.
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options