Here is a related question.
If the argument is that .mobi is not needed because the mobile content can be addressed by using browser detection, theoretically, the same could be true of .mobi sites being able to serve different content and/or css based on browser detection.
If so, does CSS@media work reliably? I found some info that some of the mobile browsers are not css compliant and will render css based on "screen" as opposed to "handheld". However the info was 2 years old.
It would be nice to service all visitors with the same database driven content & just remove some of the bells & whistles on the mobile.css.
I am not a natural born coder - so forgive me if the question is silly.
^ figured this out. I think....
...for mobile sites load mobile.css as default & use javascript to detect browser width >750 then load screen.css. My new phone is coming in next week. I'll test it then.
If i got you correct, .mobi specifications using xHTML will NOT serve all mobile devices, I would say that you are correct. In Japan, where i live and work as a mobile website developer, NTT DoCoMo uses cHTML and xHTML. But if you use RUBY ON RAILS, it will work.