viewing posts

[emaz...@cogeco.ca]

Hi, just joined this group and I can't see any of the postings. When I
click on any one, I get a blank page? Any ideas? (Windows XP, IE 9)
Thanks,
Elio

[Tony Gravagno]

> From: emazzucco

I was asked about this today and my response was to use the browser
developer plugin to see where traffic got dropped. Now that you
mention it, Elio, I had this issue with another Google service and IE
the other day. There is definitely something new going on with Google
and IE9.

The following info from Google may help. However, I was just
experimenting with IE9 and I now have no problem seeing postings in
this group with compatibility mode on or off. This might be related to
the difference between the Old and New Google Groups.
http://support.google.com/mail/bin/answer.py?hl=en&answer=181472

I recommend that anyone with this issue should think with your
programmer hat on: Make one change at a time, test, repeat. If you
suddenly get it to work, undo whatever you just did and see if it
fails again. Then for anyone who does find a solution, please post
here.

T

[Ross Ferris]

I think you will find this is actually "deliberate", and is the latest
salvo in the Google/Microsoft "war" that shifted up a gear mid-Feb
when Microsoft started flagging google.com as a malicious site --> I
think Google "defense" is they are simply adhering to standards & not
their fault IE9 is non-compliant.

When I first started getting hit with this a few weeks ago I simply
switched to Chrome for everything Google (though Firefox seems
faster!!)

On Mar 2, 9:30 am, "Tony Gravagno" <bacj8kp...@snkmail.com> wrote:
> > From: emazzucco
> > Hi, just joined this group and I can't see any of the postings. When
> I
> > click on any one, I get a blank page? Any ideas? (Windows XP, IE 9)
> > Thanks, Elio
>
> I was asked about this today and my response was to use the browser
> developer plugin to see where traffic got dropped. Now that you
> mention it, Elio, I had this issue with another Google service and IE
> the other day.  There is definitely something new going on with Google
> and IE9.
>
> The following info from Google may help. However, I was just
> experimenting with IE9 and I now have no problem seeing postings in
> this group with compatibility mode on or off. This might be related to

> the difference between the Old and New Google Groups.http://support.google.com/mail/bin/answer.py?hl=en&answer=181472

[Tony Gravagno]

Personally I'd prefer to understand the problem rather than switching
platforms.
(Holds true for browsers, databases, programming languages, operating
systems...)

[Tony Gravagno]

I've found a few common resolutions to this, outside of switching browsers, re-installing IE, or reformatting the hard drive.

 

DOCTYPE references in HTML are interpreted differently in every browser. Your browser might be using "quirks mode" to display some pages with varying doc types, and a blank page may be the result. See this page for some info:

http://andrewheins.posterous.com/ie-doctype-and-document-modes 

Note that it describes using F12 to see what mode your IE browser is in.

This is related to Compatibility Mode and the possible resolution mentioned here:

http://support.google.com/mail/bin/answer.py?hl=en&answer=181472

This thing about doctypes is not new, it's been with us since the beginning. This article from a decade ago explains it quite well:

http://www.alistapart.com/articles/doctype/

 

Hardware acceleration (GPU rendering) is on by default in IE. This seems to be affecting a lot of people. Disable through Tools>Internet Options>Advanced (tick "Use software rendering instead of GPU"), and restart.

 

Some people also associate this with 32/64 bit versions of IE or Win7. I know the OP is running XP so I'm guessing he has one of the above issues.

 

HTH

[Kevin King]

This is not directly related to the OP, but being how we're discussing IE I thought it might be useful to share an IE issue we faced recently.  Maybe this could save someone the time we went through to find the resolution.

IE8, for whatever reason, has no support for the CMYK colorspace in JPG images.  If you have a JPG image that uses this colorspace, IE will find the image, and then render it was a red X - as if the image was not found.  The only solution we found was to convert all of our images (5000+) to the RGB colorspace.  IE9 does not have this problem, so apparently someone at Microsoft figured out that CMYK support was important.

The browser incompatibilities are really not much different than terminal emulation incompatibilities that we've faced for decades except that Microsoft with IE acts like they can write their own rules - irrespective of the rest of the world - and everyone can just deal with the fallout.  IE9 seems to be a step towards compatibility, but at this point they're so far off the beaten path (especially with CSS support) that by the time IE catches up to the other browsers the other browsers will be another hundred miles down the road with additional features.  And then there's the situation where a company will standardize on a browser (say, IE8) and won't even consider upgrading the enterprise until a couple new releases come out, to avoid being on the bleeding edge.  So unfortunately, we're stuck with these turds for a while yet.

But that brings me to an interesting observation.  Doesn't it seem like the even numbered releases of IE are awful and the odd numbered releases are ... less so?

-K

--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+un...@googlegroups.com
For more options, visit http://groups.google.com/group/mvdbms

[Kevin Powick]

On Sunday, 4 March 2012 10:12:02 UTC-5, Kevin King wrote:

 

...... except that Microsoft with IE acts like they can write their own rules - irrespective of the rest of the world - and everyone can just deal with the fallout.

Reminds me of an old joke.  

Q:  How many Microsoft programmers does it take to change a lightbulb?

A:  None.  Darkness just becomes the new standard.

--

Kevin Powick 

[Bob Rasmussen]

It was my understanding (which I don't have time to verify right now) that
the HTTP standard does not include support for JPG, so support for ANY JPG
in a browser is "above and beyond". Can anyone verify this?

> > *http://andrewheins.posterous.com/ie-doctype-and-document-modes*<http://andrewheins.posterous.com/ie-doctype-and-document-modes>

Regards,
....Bob Rasmussen, President, Rasmussen Software, Inc.

personal e-mail: r...@anzio.com
company e-mail: r...@anzio.com
voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
fax: (US) 503-624-0760
web: http://www.anzio.com
street address: Rasmussen Software, Inc.
10240 SW Nimbus, Suite L9
Portland, OR 97223 USA

[Dan McGrath]

I think the real issue is that the JPEG standard didn't actually
support the CMYK colorspace. JPEG 2000 does, but has a different
extension (*.jp2).

While I'm not the biggest fan of MS, I don't think I would blame them
for not implementing a 'Adobe Special' in their IE8 browser. We cannot
complain when they don't follow standards and straight after complain
that they do, can we?

(although, I think you are right bob: I don't think HTML4 specifics
the image formats supported)

[Kevin Powick]

On Sunday, 4 March 2012 11:39:39 UTC-5, Bob Rasmussen wrote:

 

It was my understanding (which I don't have time to verify right now) that
the HTTP standard does not include support for JPG, so support for ANY JPG
in a browser is "above and beyond". Can anyone verify this?

I think you mean HTML, right?  HTTP is the transport protocol.

Regardless, HTML is just a markup language that has the <IMG> (image) tag which in itself does not define or restrict the format of the image resource specified by the tag's "SRC" attribute.  So, what you're really probably asking is whether or not JPG support is standard in web browsers.  The answer is yes, and has been for quite some time.

http://en.wikipedia.org/wiki/Comparison_of_web_browsers

--

Kevin Powick

[emaz...@cogeco.ca]

Hi Tony,
My problem seems to have resolved itself. I can see the posts now. I
did not change anything, so I'm not sure what it was.

Thanks,
Elio

On Mar 1, 5:30 pm, "Tony Gravagno" <bacj8kp...@snkmail.com> wrote:
> > From: emazzucco
> > Hi, just joined this group and I can't see any of the postings. When
> I
> > click on any one, I get a blank page? Any ideas? (Windows XP, IE 9)
> > Thanks, Elio
>
> I was asked about this today and my response was to use the browser
> developer plugin to see where traffic got dropped. Now that you
> mention it, Elio, I had this issue with another Google service and IE
> the other day.  There is definitely something new going on with Google
> and IE9.
>
> The following info from Google may help. However, I was just
> experimenting with IE9 and I now have no problem seeing postings in
> this group with compatibility mode on or off. This might be related to

> the difference between the Old and New Google Groups.http://support.google.com/mail/bin/answer.py?hl=en&answer=181472

[Eugene Perry]

Same here. I suspect that Google was doing something. Now, I get a
message about a new interface.

I took a look at their new interface and do not like it. I like being
able to tell what thread has a new message and go right to it.

Eugene

> > T- Hide quoted text -
>
> - Show quoted text -

[Ross Ferris]

IE6 was AOK!

> On Sat, Mar 3, 2012 at 10:08 PM, Tony Gravagno <bacj8kp...@snkmail.com>wrote:
>
>
>
> > I've found a few common resolutions to this, outside of switching
> > browsers, re-installing IE, or reformatting the hard drive.
>
> > DOCTYPE references in HTML are interpreted differently in every browser.
> > Your browser might be using "quirks mode" to display some pages with
> > varying doc types, and a blank page may be the result. See this page for
> > some info:

> > *http://andrewheins.posterous.com/ie-doctype-and-document-modes*<http://andrewheins.posterous.com/ie-doctype-and-document-modes>

>
> > Note that it describes using F12 to see what mode your IE browser is in.
> > This is related to Compatibility Mode and the possible resolution
> > mentioned here:
> >http://support.google.com/mail/bin/answer.py?hl=en&answer=181472
> > This thing about doctypes is not new, it's been with us since the
> > beginning. This article from a decade ago explains it quite well:
> >http://www.alistapart.com/articles/doctype/
>
> > Hardware acceleration (GPU rendering) is on by default in IE. This seems
> > to be affecting a lot of people. Disable through Tools>Internet
> > Options>Advanced (tick "Use software rendering instead of GPU"), and
> > restart.
>
> > Some people also associate this with 32/64 bit versions of IE or Win7. I
> > know the OP is running XP so I'm guessing he has one of the above issues.
>
> > HTH
>
> > --
> > You received this message because you are subscribed to
> > the "Pick and MultiValue Databases" group.
> > To post, email to: mvd...@googlegroups.com
> > To unsubscribe, email to: mvdbms+un...@googlegroups.com

> > For more options, visithttp://groups.google.com/group/mvdbms- Hide quoted text -

[Dick Thiot]

Ross,

I thought that it was IE 6.5 that was OK and wondered if that was an "odd" release.

Dick