Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the WWW-Mechanize CPAN distribution.

Report information
The Basics
Id: 6399
Status: rejected
Priority: 0/
Queue: WWW-Mechanize
People
Owner: Nobody in particular
Requestors: sdrabble [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Sun May 23 18:18:39 2004 sdrabble [...] cpan.org - Ticket created
Subject: XHTML support
WWW::Mechanize-1.02 This is perl, v5.8.0 built for i586-linux-thread-multi Stock SuSE 8.2 2.4.20-4GB with a couple of patches. There is currently no support for XHTML/1.0-Strict, which means things like name-based form submission fail. XHTML/1.0 does not allow the 'name' attribute for forms, only 'id'. Are there plans to add XHTML/1.0 compliance? Lacking it means I cannot use WWW::Mechanize to write tests for XHTML/1.0-Strict compliant sites.
  Mon May 24 11:48:38 2004 andy [...] petdance.com - Correspondence added
Date: Mon, 24 May 2004 10:48:54 -0500
From: Andy Lester <andy [...] petdance.com>
To: via RT <bug-WWW-Mechanize [...] rt.cpan.org>
CC: undisclosed-recipients: ;
Subject: Re: [cpan #6399] XHTML support
RT-Send-Cc:
Show quoted text
> There is currently no support for XHTML/1.0-Strict, which means things > like name-based form submission fail. XHTML/1.0 does not allow the > 'name' attribute for forms, only 'id'. Are there plans to add XHTML/1.0 > compliance? Lacking it means I cannot use WWW::Mechanize to write tests > for XHTML/1.0-Strict compliant sites.
I have no plans for it. If someone wants to send me patches, I'm open to them. xoa -- Andy Lester => andy@petdance.com => www.petdance.com => AIM:petdance
  Wed Oct 12 14:16:25 2005 SREZIC [...] cpan.org - Correspondence added
From: srezic [...] cpan.org
[PETDANCE - Mon May 24 11:48:38 2004]: Show quoted text
> > There is currently no support for XHTML/1.0-Strict, which means
> things
> > like name-based form submission fail. XHTML/1.0 does not allow the > > 'name' attribute for forms, only 'id'. Are there plans to add
> XHTML/1.0
> > compliance? Lacking it means I cannot use WWW::Mechanize to write
> tests
> > for XHTML/1.0-Strict compliant sites.
> > I have no plans for it. If someone wants to send me patches, I'm open > to them. >
It seems that's just necessary to extend the is_html() check. Now it just checks for "text/html" (and this could also be wrong, because some servers tend to append the charset to the Content-Type HTTP header, e.g. "Content-Type: text/html; charset=utf-8" --- will this be stripped). XHTML compatible content types are: * application/xhtml+xml * application/vnd.wap.xhtml+xml * text/xhtml Maybe also the HTML::Parser should also be set to xml_mode(1), but in my first quick test it worked without this change. Regards, Slaven
  Wed Oct 12 14:32:13 2005 mark [...] summersault.com - Correspondence added
Date: Wed, 12 Oct 2005 13:31:10 -0500
From: Mark Stosberg <mark [...] summersault.com>
To: Slaven_Rezic via RT <bug-WWW-Mechanize [...] rt.cpan.org>
Subject: Re: [cpan #6399] XHTML support
RT-Send-Cc:
On Wed, Oct 12, 2005 at 02:16:26PM -0400, Slaven_Rezic via RT wrote: Show quoted text
> > It seems that's just necessary to extend the is_html() check. > Now it just checks for "text/html" (and this could also be wrong, > because some servers tend to append the charset to the Content-Type > HTTP header, e.g. "Content-Type: text/html; charset=utf-8" --- will > this be stripped). XHTML compatible content types are: > * application/xhtml+xml > * application/vnd.wap.xhtml+xml > * text/xhtml > > Maybe also the HTML::Parser should also be set to xml_mode(1), but in > my first quick test it worked without this change.
Slaven, Thanks for the research. This sounds easy enough. Would you willing to donate some automated tests and the actual patch to the project to confirm it works? I agree, XHTML support would be nice to have. Mark
  Sun Aug 26 23:18:01 2007 PETDANCE [...] cpan.org - Status changed from 'new' to 'rejected'