You are right Ralph,
but first I have to have a working CakePHP application that actually
get's used. If that is the case I will aim for HTML 4 STRICT (and
later on HTML 5 STRICT or LOOSE let's see) and having website/
application quality in mind I will for sure be remembered on this
thread by
Yep I agree. MSIE 5 through 7, the most popular browser, treats XHTML
as usual HTML. So there's no point.
And by the way speaking of the future, there is no XHTML 2.0 in it,
only HTML 5, which is actively developed now.
S.
On Dec 27, 12:54 pm, gearvOsh mileswjohn...@gmail.com wrote:
Honestly
I think Adams answer is the only sane one here, that looks to be the
official way to change tag definitions after the app/config/tags.php
was deprecated almost 2 years ago ( https://trac.cakephp.org/ticket/2081
)... No need to override html helper, no need to pass everything
through htmltidy.
@gearvOsh - Thanks for pointing this out. I finally came to reading it
all, and I now personally find that this issue is to be seen as a
weakness of the CakePHP framework. I sadly do not possess the
knowledge at the moment to think up a good performance friendly simple
solution to solve the
Just one question, because the thread opener has a point (XHTML and
HTML4 both have their benefits as HTML5 will probably have but XHTML2
seems not going to have):
Is there a CakePHP global way to define output type (XHTML 1.0, 1.1
HTML 4, all 3 strict, transitional, frameset) - if not, it is
I have not found any option or setting for using HTML or XHTML.
All I have seen is that you can set the Doctype, but even if you set
the Doctype as HTML, all the tags are in XHTML.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
Is it possible that you can just overwrite the tag list with your HTML
equivalents?
http://bakery.cakephp.org/articles/view/overriding-specific-html-tags-before-using-helper-methods
Cheers,
Adam
On Dec 29, 8:24 am, gearvOsh mileswjohn...@gmail.com wrote:
I have not found any option or setting
No thats the thing, XHTML is not supported.
You would need to put the content-type as application/xhtml+xml which
in most cases breaks the layout and always breaks IE. Everyone usually
puts it as text/html which then renders the browser as regular HTML
and NOT XHTML. Im not telling you XHTML is
Well I personally would say that having the taglist in XHTML / XML is
of a more global advantage ...
Since if you want to spit out XML for other Documents eg. AJAX, RSS,
and so on you need tags that confirm to XML for it to even work. And
as far as I know RSS Readers etc. wont let you get away
gearvOsh wrote:
In CakePHP you can choose the Doctypes of XHTML or HTML but the
taglist is all XHTML, which then causes markup errors.
gearvOsh,
It shouldn't be too much of hassle to create a html4 helper based on
the existing html helper. If you create your helper extending the
On Sat, Dec 27, 2008 at 12:43 PM, Bernardo Vieira
bvieira.li...@gmail.com wrote:
gearvOsh wrote:
In CakePHP you can choose the Doctypes of XHTML or HTML but the
taglist is all XHTML, which then causes markup errors.
gearvOsh,
It shouldn't be too much of hassle to create a html4 helper
On Sat, Dec 27, 2008 at 4:22 AM, gearvOsh mileswjohn...@gmail.com wrote:
No thats the thing, XHTML is not supported.
You would need to put the content-type as application/xhtml+xml which
in most cases breaks the layout and always breaks IE. Everyone usually
puts it as text/html which then
On Sat, Dec 27, 2008 at 10:47 AM, Marcelo Andrade mfandr...@gmail.com wrote:
On Sat, Dec 27, 2008 at 12:43 PM, Bernardo Vieira
bvieira.li...@gmail.com wrote:
gearvOsh wrote:
In CakePHP you can choose the Doctypes of XHTML or HTML but the
taglist is all XHTML, which then causes markup
@Arthur Pemberton - Yeah but then if I set my Doctype as HTML 4 im
riddled with markup errors which isnt good for me or the client.
@Marcelo Andrade - Yeah thats what I was hoping was in the system, but
I guess not. Ill see if I can extend it in some way.
Honestly I really dislike the xhtml type of tags in CakePHP. There
are no reasons for that, I think it would be a better idea to make it
html 4 strict.
Heres an article on why xhtml is retarded.
http://www.webdevout.net/articles/beware-of-xhtml
On Fri, Dec 26, 2008 at 10:54 PM, gearvOsh mileswjohn...@gmail.com wrote:
Honestly I really dislike the xhtml type of tags in CakePHP. There
are no reasons for that, I think it would be a better idea to make it
html 4 strict.
Heres an article on why xhtml is retarded.
Please explain your cleanliness? HTML 4 can do everything XHTML can
except self closing tags /.
Also your XHTML is being parsed as HTML and removed, so whats your
point?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Everyone has reasons for and against various technologies.
Thankfully, CakePHP provides you a complete fantastic framework without
limiting you to something as specific as only being able to use xhtml.
You should be able to extend the html helper for all (most?) the tags
you want to produce.
On Sat, Dec 27, 2008 at 12:32 AM, gearvOsh mileswjohn...@gmail.com wrote:
Please explain your cleanliness? HTML 4 can do everything XHTML can
except self closing tags /.
Also your XHTML is being parsed as HTML and removed, so whats your
point?
What exactly is CakePHP doing that you find
Most browsers dont support XHTML and most people dont even write XHTML
correctly. If this is your site(http://www.pembo13.com/), your DTD is
XHTML but its being parsed as HTML. So basically thats kaput, did you
read the article I posted earlier?
@Graham Weldon - Seems like a lot of work to
On Sat, Dec 27, 2008 at 1:41 AM, gearvOsh mileswjohn...@gmail.com wrote:
Most browsers dont support XHTML
I don't know, all the sites where I use XHTML seem to work just fine.
and most people dont even write XHTML
correctly.
Not exactly my problem now is it. That's kinda like saying don't
21 matches
Mail list logo
