Description of problem: The fact we have small warning in the login page is not enough. The fact is, there are some severe issues when working with it. For example, you cannot set a static IP to a NIC - it's not enabled! This already led to several false positive bug reports from QE, and surely will cause Support issues. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I don't think we should block it, just enhance the message about the browser not supporting the GWT tech well enough. Completely blocking something off doesn't look good, IMO
(In reply to comment #1) > I don't think we should block it, just enhance the message about the browser > not supporting the GWT tech well enough. Completely blocking something off > doesn't look good, IMO I didn't think so either - but I've been convinced that it'll cause issues.
but it is useful for just browsing/looking around, so also not sure we should block it.
(In reply to comment #3) > but it is useful for just browsing/looking around, so also not sure we > should block it. Unless you forget it's just for browsing/looking around, as happens often in QE - and we file bugs that don't reproduce on others' - till we figure out it's Chrome. That's my main concern. It's not that it looks bad or something - behavior is inconsistent. I'm not even talking about the difference I see in behavior *between chrome versions*.
in this case, I've one RFE as well: blocking IE8 (non-compliance with standards, terrible slow{as result of using JS}, drag & drop doesn't work). the similar with IE9 except slowness The customer can have an impression that our product looks/behaves unusable.
(In reply to comment #5) > in this case, I've one RFE as well: > > blocking IE8 (non-compliance with standards, terrible slow{as result of > using JS}, drag & drop doesn't work). I disagree. There's a big difference between working slow and working wrong. > > the similar with IE9 except slowness > > The customer can have an impression that our product looks/behaves unusable. I am surprised, however, that this probably still the most popular IE version - http://en.wikipedia.org/wiki/Internet_Explorer#Desktop_Market_share_by_year_and_version (although stats are not up-to-date). One reason may be because it's the latest (and last) IE supported on XP.
I don't agree with blocking Chrome - we need to find the bugs and fix them, if we can't log into the portal then this won't happen.
Product Management has reviewed and declined this request. You may appeal this decision by reopening this request.