It solves it. There is no sidesteping.
not really.
>If it won't render a simple mobile site, who knows what else it can't render.
Who knows? Who cares? Maybe you should write a book about it. Devote
the rest of your life to catalog every single f.cking web application that
doesn't work on one particular version of one particular browser on one
particular system runing one particular operating system.
I don't see what the problem is. If you have one website that your main browser
can't handle, yet you have a different browser that'll handle it then the
problem is solved. Completely. Make a note to check future versions of your
main browser, perhaps, but get on with your f.cking life.
Do you see people complaining that they can't find any decent cars that can do
0-60 in under 5 seconds, seat ten, get 50mpg, and haul the contents of a 4000
square foot house?
No. There are specialized vehicles and nobody is stupid enough to
expect one particular model to do everything. Ditto for web browsers.
> >Installing a new browser doesn't solve the problem as much as it sidesteps
> >it.
> It solves it. There is no sidesteping.
Again, I would agree IF all phones running IE Mobile exhibited the problem,
but they don't. Just a very small number. Where I come from, that's
called a "bug." Ignoring the bug by using different software isn't fixing
the bug. That's a sidestep, IMO.
> >Other models of phone, running essentially the same browser don't have
> >the same problem. I find that interesting.
> not really.
You mean YOU don't find it interesting. Fair enough. Your lack of
interest is noted, yet you're apparently interested enough to complain
about Roger not following your advice, or anyone trying to deduce the
problem.
> >If it won't render a simple mobile site, who knows what else it can't render.
> Who knows? Who cares? Maybe you should write a book about it. Devote
> the rest of your life to catalog every single f.cking web application that
> doesn't work on one particular version of one particular browser on one
> particular system runing one particular operating system.
But that's just it- THAT'S not the case if you've read the entire
(apparently uninteresting) thread- the SAME VERSION of the SAME BROWSER on
the SAME OS behaves differently on different models of phone. Again, where
I grew up, we call that a bug.
> I don't see what the problem is. If you have one website that your main browser
> can't handle, yet you have a different browser that'll handle it then the
> problem is solved. Completely.
True. Arguably, he could also just bin the phone, switch providers, and
buy a new one. Alternatively, he could forsake all electronics and
technonogy, build a log cabin in the woods, and live off the land. There
are many solutions- and yours is certainly an easy one. (Roger's was also
easy- bookmark the Google reformatted page and use that, which is also a
sidestep.)
> Make a note to check future versions of your
> main browser, perhaps, but get on with your f.cking life.
Christ, it's just an intellectual exercise, not my life's work. I enjoy
the odd bit of troubleshooting and problem solving- it keeps the mind
sharp. Some people play sudoku... One evening recently when I had nothing
better to do, I tried to figure out why my son's recently-upgraded-to-Vista
PC no longer played dialog sounds in two of his RPG games (from the same
vendor- ironically Microsoft), but still played music and sound effects
even though ALL game sounds (those that worked and those that didn't) were
just 128k bitrate MP3s, and all played just fine under XP. The dialog
clips that wouldn't play in the game also wouldn't play in WMP.
To troubleshoot, I e-mailed a few to myself and discovered they'd play in
WMP in EVERY other PC in the house- whether XP or Vista and even on my PPC
phone. I played with different audio drivers, adding/removing codecs,
analyzed with GSpot and graphedit for awhile, but by hour #3, I threw in
the towel and sidestepped. (Even I will only waste so much time on a
purely intellectual exercise!) I sidestepped by batch re-encoding all of
the dialog files for both games to .wma and back to .mp3 and they now
worked- whatever the PC didn't like about original files was obliterated by
the re-encoding.. I saved the original versions in case I ever want to
"reopen the case" (unlikely unless we run into more .mp3s or games that
refuse to play.)
> Do you see people complaining that they can't find any decent cars that can do
> 0-60 in under 5 seconds, seat ten, get 50mpg, and haul the contents of a 4000
> square foot house?
>
> No. There are specialized vehicles and nobody is stupid enough to
> expect one particular model to do everything. Ditto for web browsers.
Yes, but if your red sports car did 0-60 in 5 seconds, and my blue one with
the same body, engine, and transmission, did it in 20, I'd consider mine
defective. The issue isn't that "IE Mobile" itself can't render a
particular WAP page, but that HIS copy of it can't, where virtually all
others, older, newer and the same, can. At the risk of repeating myself,
that's a bug, and Microsoft, HTC, and/or Sprint shouldn't be let off the
hook just because an alternate browser is available.
Where we ARE in agreement is that the issue is only worth so much time
worrying about. We just differ in how MUCH time! Sadly, you and I have
spent/wasted more time debating the merits of it than anyone has spent
trying to troubleshoot it.
If Roger is still reading, at this point, I'm drawing a blank, and since I
have no device it doesn't work on, I'm unable to troubleshoot it further.
At this point, I'd contact Sprint and HTC and put the ball in their courts
(knowing full well that in all likelyhood nothing will be done about it,
particularly since HTC's usual bug-fix advice is "buy the next model.")
Roger 2008 - 15 May 2008 23:48 GMT
> If Roger is still reading, at this point, I'm drawing a blank, and since I
> have no device it doesn't work on, I'm unable to troubleshoot it further.
> At this point, I'd contact Sprint and HTC and put the ball in their courts
> (knowing full well that in all likelyhood nothing will be done about it,
> particularly since HTC's usual bug-fix advice is "buy the next model.")
Please give up on Al. I've been through that "New Browser" routine with him
before and there is no stopping him.
As for my Mogul. I know someone that says he has m.tvguide.com working on
his Mogul along with other things like WM6.1 so I'm going to try everything
he did.