Opacity of active data layers resets when changing to or from the Custom basemap

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Change the opacity of an active data layer so that it is not completely 
opaque.
2. If the current basemap is Custom, change the basemap to Google Terrain, 
Google Satellite, or OpenStreetMap. If the current basemap is not Custom, 
change the basemap to Custom. The opacity of the active data layer will reset 
so that it is completely opaque.

What is the expected output? What do you see instead?
The expected output is that the user could change the basemap to or from the 
Custom basemap and the opacity of the active data layers would not change. 
Instead, the opacity of the active data layers resets to 100% when a user 
changes to or from the Custom basemap.

Please use labels and text to provide additional information.
If a user switches between the Google Terrain, Google Satellite, and 
OpenStreetMap basemaps, then the opacity of the active data layers does not 
reset.

Tested MORIS v. 0.35 on Windows 7 and Firefox 3.16.15.

Original issue reported on code.google.com by emily.hu...@state.ma.us on 8 Mar 2011 at 9:35

[GoogleCodeExporter]

Fixed.

Committed revision 60.

Original comment by cpl...@gmail.com on 19 Aug 2011 at 4:10

• Changed state: Fixed

[GoogleCodeExporter]

This worked for me.
Firefox 6
Safari 5.1
Chrome 13.0
IE 8.0

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

[GoogleCodeExporter]

Good in IE 9.

Original comment by daniel.s...@state.ma.us on 25 Aug 2011 at 6:32

[GoogleCodeExporter]

Works for me. Tested with Chrome 14, Firefox 6, IE 9, and Safari 5.1 on Windows 
7.

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

• Changed state: Verified