Thread: php???
View Single Post
Old 01-24-2014, 02:29 PM   #9
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by AnotherCat View Post
If the problem is the previously mentioned on they are the correct format so no issue except for the filename.

Just because you hate IE doesn't make your shouting about it of any value to the matter, nor of any interest to those more open minded.

For the only naming instances I have come across it has been a server end problem. MobileRead was fixed once, but seems to have reverted again (there have been a number of threads about this over the last year or so). On another small site I use the epubs once started getting named as zips , the site owner corrected the problem immediately when informed of the issue, so was only fleeting.

As I say, it is just a case of adding the site to the compatability list where it will probably be lonely as of the many of the other sites I visit it is the only one non compliant.
I only hate IE because it does weird things which no other browser does. It is not a matter of MobileRead being non-compliant, it is Microsoft which doesn't follow the standards. According to mrmikel, it is the ActiveX part of IE that is causing it. A clear case of useless Microsoft "features" that interfere with what a browser should be doing. Do you realize that good web developers have to code two versions of their website, one for IE and one for "all other browsers"? And some just won't bother, and tell you to upgrade to a real browser.

Any problem which is only present in IE is obviously a problem with IE. This problem has yet to be reported (to my knowledge) anywhere other than in IE.
eschwartz is offline   Reply With Quote