Application does not fully work with Safari 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. 

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. 

The issues are the same as described for the Chrome browser is Issue #4 
http://code.google.com/p/morisoliver/issues/detail?id=4 The screenshots from 
Issue #4 would be identical. 

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

• Merged into: #4

[GoogleCodeExporter]

Application was tested with Windows XP and Safari 5.0.3 (7533.19.4)

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

[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:12

• Added labels: Usability

[GoogleCodeExporter]

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

• Added labels: Browsercompatibility
• Removed labels: Usability

[GoogleCodeExporter]

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

• Added labels: Browser
• Removed labels: Browsercompatibility

[GoogleCodeExporter]

I think I've fixed this.  It had to do w/ how Safari & Chrome handled namespace 
prefixes (things like wfs:tagName) which do come back as part of the WMS 
results.

Committed revision 58.

I had to specify the namespaces in the code.  See the svn comment . . .

Test to see if document.getElementsByTagNameNS exists.  If so, use it.  
Otherwise search by 'ns:tag'
, the old fashioned way.

This assumes that the namespaces don't change!

http://www.opengis.net/wfs
and
http://www.w3.org/2001/XMLSchema

Original comment by cpl...@gmail.com on 17 Aug 2011 at 8:12

• Changed state: Fixed

[GoogleCodeExporter]

Identify and extract worked in Safari 5.1

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

[GoogleCodeExporter]

Identify and extract worked for me. Tested with Safari 5.1 on Windows 7.

Original comment by emily.hu...@state.ma.us on 23 Sep 2011 at 1:15

• 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]

I think I'm having 2nd thoughts about having us spin up new issues.  Maybe it 
shouldn't matter, but I'd really to keep the issues:SOW as 1:1 as possible.  
Let's leave the new issue 72 as an exception to this rule, but for future 
reference, do you agree that this is doable?

Original comment by cpl...@gmail.com on 3 Oct 2011 at 6:53

[GoogleCodeExporter]

Sure. Sorry for the confusion. Would you like me to merge Issue 72 into this 
one?

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

[GoogleCodeExporter]

That would be super.  Thanks.

Original comment by cpl...@gmail.com on 3 Oct 2011 at 7:07

[GoogleCodeExporter]

Issue 72 has been merged into this issue.

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

[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:10

• 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:51

• 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:46

Attachments:

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

[GoogleCodeExporter]

I'll see what I can do w/ this once the poly query has been unbroken.  I think 
I need to chalk this off as a bug that is not solvable on my end, but I'll wait 
and see.

Original comment by cpl...@gmail.com on 21 Nov 2011 at 3:35

[GoogleCodeExporter]

I'm rolling issues 4 and 7 into one.

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

• Changed state: Duplicate