|
Quotes |
" ... I want to tell you that your thyme product is functional and valuable beyond
words. I cannot imagine why any portal would be without it. It is the cornerstone of our new project ..."
" ... Thanks for such a complete project, its making my job much easier. ..."
" ... I have now deployed 4 different calendars and our users love them ... "
" ... Easy to install and use and a great look/design. ..."
" ... This has to be the easiest to use program I think I've had to deal with at all this year. ..."
|
|
| View previous topic :: View next topic |
| Author |
Message |
eFlux Guest
|
Posted: Tue Nov 14, 2006 12:20 am Post subject: XHTML 1.0 compliance, single quoted HTML tags, etc |
|
|
Hello,
First off let me say that I have installed Thyme and have been using it for a few hours now. It looks to be a very nice piece of software. I do have some concerns that I hope you can respond to.
They are:
For the most part, you have started to migrate from HTML to XHTML 1.0. Is there a plan to completely migrate to XHTML 1.0 compliancy?
The single quoted attributes on the HTML tags causes some browsers to display incorrectly and causes errors when validating. Are their plans to conver to double quotes for attributes?
Instead of opening links with target values of _new, are there plans to convert to javascript window.open functions?
I realize that some of these items could take a significant amount of time but I am wondering what your thoughts are on XHTML 1.0 compliance and if you plan to pursue it. |
|
| Back to top |
|
 |
esoft_ian
Joined: 12 Sep 2005 Posts: 5275
|
Posted: Tue Nov 14, 2006 2:35 am Post subject: |
|
|
Hi,
XHTML compliance It is on the radar, but far down on the list of requests.
There is no preference of double quotes vrs single quotes that I am aware of. At least not in HTML 4.0 transitional. If you have something that says otherwise I'd love to take a look. Could you provide an example of a browser that does care if single or double quotes is used and the tag / attribute? I know Safari has some issues with JavaScript within a single quoted href attribute (without regard to any documented standard favoring one over the other), but other than that I'm not aware of anything. The next version of Thyme is being developed with this in mind, but if there is something else I should make note of I'd love to have it pointed out.
The only thing that uses a target=_new is the printable link. The event window uses window.open().
In summary .. XHTML compliance is not a very high priority.
Let me know if you have any more questions. |
|
| Back to top |
|
 |
eFlux Guest
|
Posted: Tue Nov 14, 2006 3:16 am Post subject: XHMTL Compliance |
|
|
Thanks for the reply.
The reason I would like to see double quotes for attributes is because it is a part of XHTML 1.0 strict compliancy (as far as I know). I'm sure it works fine for HTML 4.0 transitional. I can't think of any browsers off hand that have issues with single quoted attributes.
I use an open source CMS called Xaraya. It started as a fork of PHPNuke (or PostNuke I can't remember). Xaraya outputs 100% XHTML 1.0 strict compliant code and I strive to do the same in all modules I develop for the CMS. So, if I want to embed a calendar into my XHTML 1.0 strict website there goes my XHTML 1.0 compliancy unless I want to use RSS feeds or something like that.
I guess I can live with it for how nicely featured the calendar is. Thanks again! |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|