Application does not fully work with Chrome web browser

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Draw up a datalayer such as hospitals, make sure hospitals are seen in your 
view.
2. Choose the Identify tool and draw a box around some hospitals.
3. OR, click the Export data button to extract data, and click the next button 
twice to get to Step 3 of 5 where Query results are shown. 

What is the expected output? What do you see instead?
The expected output is a non-none amount of features. For Identify, although 
the orange box is clearly around some hospitals, none are found.  For the 
Export data button, although hospitals are clearly in the map view, none are 
found. 

Please use labels and text to provide additional information.

Although the mapping portion (WMS) of the program works (datalayers draw, tools 
to zoom around the map work), the identify and extract functions (WFS) do not 
work.  Queries on the datalayers always produce "none" features. 

Original issue reported on code.google.com by Aleda.Fr...@state.ma.us on 17 Feb 2011 at 4:04

Attachments:

• chrome_identify_problem.png
• chrome_extract_problem.png

[GoogleCodeExporter]

Application was tested with Windows XP and Chrome 9.0.597.98

Original comment by Aleda.Fr...@state.ma.us on 17 Feb 2011 at 4:05

[GoogleCodeExporter]

Tested with MORIS v. 0.35

Original comment by Aleda.Fr...@state.ma.us on 18 Feb 2011 at 2:15

[GoogleCodeExporter]

Original comment by Aleda.Fr...@state.ma.us on 24 Feb 2011 at 7:11

• Added labels: Usability

[GoogleCodeExporter]

Original comment by Aleda.Fr...@state.ma.us on 24 Feb 2011 at 8:58

• Added labels: Browser
• Removed labels: Usability

[GoogleCodeExporter]

I was able to identify and extract with Google Chrome v. 13.0

Original comment by Aleda.Fr...@state.ma.us on 22 Aug 2011 at 2:08

[GoogleCodeExporter]

BTW, also fixed in Safari 5.1

Original comment by Aleda.Fr...@state.ma.us on 22 Aug 2011 at 2:21

[GoogleCodeExporter]

Identify and extract work for me. Tested with Chrome 14 on Windows 7.

Original comment by emily.hu...@state.ma.us on 22 Sep 2011 at 5:50

• Changed state: Verified

[GoogleCodeExporter]

The map turns blue in Chrome 14 and Safari 5.1 when a user double-clicks to 
finish drawing an identify or measure by area polygon. Please see Issue 72 for 
details. 

Tested MORIS v. 0.56 with Chrome 14 and Safari 5.1 on Windows 7. The map does 
not turn blue in MORIS v. 0.35 with Chrome 14 and Safari 5.1 on Windows 7.

Original comment by emily.hu...@state.ma.us on 3 Oct 2011 at 3:37

[GoogleCodeExporter]

Map turns blue after double-clicking to finish drawing poly in Chrome and 
Safari:

1. Open MORIS in Chrome or Safari.
2. Use the Identify features by drawing a polygon tool or Measure by area tool.
3. When double-clicking to finish drawing the polygon, the map turns blue.

Original comment by emily.hu...@state.ma.us on 3 Oct 2011 at 7:11

• Changed state: Started

[GoogleCodeExporter]

This requires an upgrade to OL 2.11.

Since several key issues seem to depend on OL 2.11, I have assumed that Aleda 
will point all config files to OL 2.11 beginning w/ this version, v. 0.58.

But if it turns out that an upgrade on OL 2.11 breaks other things that weren't 
laid out as issues per the SOW, I suggest that we rollback and cut some of our 
losses.

I'll poke around and paste this same message to other issues that depended on 
an OL upgrade.

Original comment by cpl...@gmail.com on 6 Oct 2011 at 1:50

• Changed state: Fixed

[GoogleCodeExporter]

The map no longer turns blue when I double-click to finish drawing a polygon in 
Chrome or Safari. When I double-click a row in the Query results window in 
Chrome or Safari, part of the window turns blue (this doesn't happen in Firefox 
or IE). Would it be possible to change this so that double-clicking doesn't 
turn the query results window blue?

Tested MORIS v. 0.62 with Chrome 14 and Safari 5.1.1 on Windows 7.

Original comment by emily.hu...@state.ma.us on 18 Oct 2011 at 7:45

Attachments:

• chrome_double-click_screenshot.png
• safari_double-click_screenshot.png

[GoogleCodeExporter]

Issue 7 has been merged into this issue.

Original comment by cpl...@gmail.com on 29 Nov 2011 at 8:29

[GoogleCodeExporter]

This issue seems to have been somewhat resolved -- maybe.  The highlighting 
only appears to be temporary.  If you double-click on a row in the at-a-glance, 
you may see the blue, but it goes away once the feature details records have 
been updated.

I think we're going to have to chalk this off as a bonafide bug.  If you click 
on the area BETWEEN the at-a-glance block and the feature-details box, you can 
see that it tries highlighting stuff completely unrelated to each block's 
functionality.

My guess is that this extjs issue has been fixed in their latest release, but 
we're at 3.3.1 while their release is up at 4.x.  That would be a major upgrade 
for us.

Original comment by cpl...@gmail.com on 29 Nov 2011 at 8:37

[GoogleCodeExporter]

Just to help show you that I'm not throwing up my hands and saying "I quit" w/o 
at least some backup, test these two examples in FF and then in Safari.

Look at the Form 3 example, and double-click to the right of Biography: -- 
anywhere in the blue background.  You should see bizarre highlighting in the 
3.3.1 example.

Do the same in the 4.0.0 example, and it should highlight the font select box.

I can still get somewhat strange highlights if I click in unexpected places in 
the 4.0.0 version, but it seems they've fixed the bulk of the focus issues 
(which is what I think is busted in 3.3.1 in those browsers).

http://dev.sencha.com/deploy/ext-3.3.1/examples/form/dynamic.html

http://dev.sencha.com/deploy/ext-4.0.0/examples/form/dynamic.html

Original comment by cpl...@gmail.com on 29 Nov 2011 at 10:25

[GoogleCodeExporter]

Incidentally, you should only need to single-click on an at-a-glance row.  I 
did look into trying to disable double-clicks to try avoiding the highlight 
strobe lights, but it turns out that it's not an option.

Original comment by cpl...@gmail.com on 29 Nov 2011 at 10:31

[GoogleCodeExporter]

Verified. Won't fix the blue highlighting in the Query results since this looks 
like an extjs bug.

Original comment by emily.hu...@state.ma.us on 6 Dec 2011 at 3:21

• Changed state: Verified