Michel, read carefully, what those registry tweaks do: they just change the user agent string.
I would almost go as far to say, that good web applications never rely on that. Don't code for a specific browser, but for features.
Of course, no matter what you code, the platform of your choice might still (ab-)use the user agent string when generating its response to the brwoser. At least Domino is wanna-be-smart enough, to do that. E.g., if your browser claims to be a current IE version, Domino generates DHTML for sections. If not, you get either a worthless triangle graphic (in edit mode) or regular round-trip-to-the-server-link (read mode).
Providing us with a fabulous example for why this is generally evel: Have Firefox identify itself as IE, and the code Domino normally serves to IE only works like a charm.
Any other aspects of the browser - from CSS interpretation to basic HTML rendering behaviour - cannot be altered that easily.
Michel, read carefully, what those registry tweaks do: they just change the user agent string.
I would almost go as far to say, that good web applications never rely on that. Don't code for a specific browser, but for features.
Of course, no matter what you code, the platform of your choice might still (ab-)use the user agent string when generating its response to the brwoser. At least Domino is wanna-be-smart enough, to do that. E.g., if your browser claims to be a current IE version, Domino generates DHTML for sections. If not, you get either a worthless triangle graphic (in edit mode) or regular round-trip-to-the-server-link (read mode).
Providing us with a fabulous example for why this is generally evel: Have Firefox identify itself as IE, and the code Domino normally serves to IE only works like a charm.
Any other aspects of the browser - from CSS interpretation to basic HTML rendering behaviour - cannot be altered that easily.