Menus on web site of French Prime Minister are horked. (governmental site, not personal site)
Can't connect right now. Webmaster contact is given on Error Page : firstname.lastname@example.org Ok, It works in N621 on Win2000. There is server side sniffing that redirects the UA to http://www.premier-ministre.gouv.fr/home_nn6.htm It shows that at least they know about N6. changing their sniffing should do the work. (but when using the menu in the N6 page, they serve an non-standard page that fails to render correctly with Mozilla.) Setting P2.
Priority: -- → P2
sent letter to mentionned contact and also to email@example.com ->Accepting bug.
Status: NEW → ASSIGNED
oops, forgot to say that I pointed to webmaster to http://developer.netscape.com/evangelism/docs/articles/find-gecko/
Got answer from firstname.lastname@example.org . The person is contacting the web developer and will consider supporting Mozilla. Target -> April.
Target Milestone: --- → Apr
reflecting URL in summary
Summary: bad menus on web site of French Prime Minister (governmental site, not personal site) → premier-ministre.gouv.fr : bad menus on web site of French Prime Minister (governmental site, not personal site)
mmm target was april, we are in june. nothing changed :*(
Following comment #4, adding [havecontact]
Whiteboard: [havefix] → [havefix][havecontact]
After I met someone from the premier-ministre.gouv.fr web team, I had a call form another member of their web team. Worked with him to solve the issue (bad Cold fusion user agent sniffing) so that they serve W3 compliant web pages to Gecko based browsers. Checked on their test server (http://www-org.premier-ministre.gouv.fr/fr/ )that the AOL US client for MacOSX, NS7, Mozilla 1.0 and 1.2a, along with K-meleon 0.6, Galeon 1.2.5 worked correctly. Marked resolved fixed. :-)
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
tech evang june 2003 reorg
Component: Europe: West → French
Target Milestone: Apr → ---
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.