nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

IE11 mouse wheel scrolling and map zoom

EdwardSohn1

I upgraded to IE11 to improve performance from IE9 and now the mouse wheel scrolling zoom in/out is affected.
Whether I scroll up/down the map only zooms in, not out.

This is not seen with IE9 nor IE10 nor chrome nor firefox.
Just IE 11.

is there a workaround...?
Quick answer would be appreciated.

Thanks.

Find more posts tagged with

Accepted answers

All comments

KevinGooss

I am having a similar issue with the rubber band for zooming.

If i have X-UA set at Edge or IE=10 i get no rubber band in IE (with any document mode) but it is always there for firefox.

ThomasBoring

I upgraded to IE11 to improve performance from IE9 and now the mouse wheel scrolling zoom in/out is affected.
Whether I scroll up/down the map only zooms in, not out.

This is not seen with IE9 nor IE10 nor chrome nor firefox.
Just IE 11.

is there a workaround...?
Quick answer would be appreciated.

Thanks.

Adding this to the <head> worked for me. Your mileage may vary.

<meta http-equiv="X-UA-Compatible" content="IE=10, chrome=1" />

derekswingley1

Well, this is embarrassing...we found that our systems people had our js_feedback email alias locked down pretty tight so our filters were preventing some emails from coming through, yours included. We've now fixed this so you should be able to email that address and it will get to us. I apologize for that. Now back to your other thread where we can discuss this editor + cut issue further.

DerivenC

Thanks. I'll also take a look at the API for 3.8 to see if the "bug" still exists. And I did verify that I sent the email to js_feedback@esri.com from my gmail.com account. Maybe it's blocking? I'll resend again right now.

edit: I'll also post the fix on the original thread. (Hope that's okay.)

derekswingley1

I spent a little more time looking into this but can't see where this is failing. Once I have your fix, I'll take a look then reply in your original thread so we don't continue to overload this with off topic posts.

derekswingley1

Thanks for taking a look at this. Unfortunately that's a different use case. Try it with the editor widgit. And if that works, try it with a regular graphics layer or featurelayer collection.

I'm looking into your test cases. I'll post back when I have more info.

You'll notice that all of the samples from the site do not include the cut tool which I found odd. Why hide it from the main site samples?

We cannot show case every option of every component of the API in a sample. We show the samples that use pieces of the API that have the broadest appeal and make other accessible via search results.

I submitted the bug fix in that email address. Couple of lines fixes the issue. You'll see where the problem is and how I fix it. It is specifically the editor-all file. (Perhaps elsewhere, not certain.)

Please confirm you emailed js_feedback@esri.com. We haven't received your email yet.

kenbuja

Sorry about that...can you post links with errors?

I've started a new thread to avoid hijacking this one.

DerivenC

Here's an example I created a few months back using a feature collection. Originally with 3.6. Just tried with 3.8 and it doesn't work. With my bug fix, it works great.

I tested these using the ArcGIS JS sandbox.

fc5.zip

DerivenC

Derek,

Tried this sample and it doesn't work right using 3.8. This is this sample with one extra line: cutVisible: true.

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <!--The viewport meta tag is used to improve the presentation and behavior of the samples 
      on iOS devices-->
    <meta name="viewport" content="initial-scale=1, maximum-scale=1,user-scalable=no">
    <title>Edit rivers and waterbodies</title>


    <link rel="stylesheet" href="http://js.arcgis.com/3.8/js/dojo/dijit/themes/claro/claro.css">
    <link rel="stylesheet" href="http://js.arcgis.com/3.8/js/esri/css/esri.css" />
    <style>
      html,body{height:100%;width:100%;margin:0;overflow:hidden;}
      #map{
        padding:0;
      }
      #header{
        font-size: 1.1em;
        font-family: sans-serif;
        padding-left: 1em;
        padding-top:4px;
        color:#660000;
      }
      .templatePicker {
        border: none;
      }


      .dj_ie .infowindow .window .top .right .user .content { position: relative; }
      .dj_ie .simpleInfoWindow .content {position: relative;}
    </style>
    
    <script src="http://js.arcgis.com/3.8/"></script>
    <script>
      var map;
      
      require([
        "esri/map", 
        "esri/tasks/GeometryService",
        "esri/toolbars/edit",


        "esri/layers/ArcGISTiledMapServiceLayer",
        "esri/layers/FeatureLayer",


        "esri/symbols/SimpleMarkerSymbol",
        "esri/symbols/SimpleLineSymbol",


        "esri/dijit/editing/Editor",
        "esri/dijit/editing/TemplatePicker",


        "esri/config",
        "dojo/i18n!esri/nls/jsapi",


        "dojo/_base/array", "dojo/parser", "dojo/keys",


        "dijit/layout/BorderContainer", "dijit/layout/ContentPane", 
        "dojo/domReady!"
      ], function(
        Map, GeometryService, Edit, 
        ArcGISTiledMapServiceLayer, FeatureLayer,
        SimpleMarkerSymbol, SimpleLineSymbol, 
        Editor, TemplatePicker,
        esriConfig, jsapiBundle,
        arrayUtils, parser, keys
      ) {
        parser.parse();       


        // snapping is enabled for this sample - change the tooltip to reflect this
        jsapiBundle.toolbars.draw.start = jsapiBundle.toolbars.draw.start +  "<br>Press <b>ALT</b> to enable snapping";
       
        // refer to "Using the Proxy Page" for more information:  https://developers.arcgis.com/en/javascript/jshelp/ags_proxy.html
        esriConfig.defaults.io.proxyUrl = "/proxy";    


        //This service is for development and testing purposes only. We recommend that you create your own geometry service for use within your applications. 
        esriConfig.defaults.geometryService = new GeometryService("http://tasks.arcgisonline.com/ArcGIS/rest/services/Geometry/GeometryServer");
        
        map = new Map("map", { 
          basemap: "satellite",
          center: [-96.541, 38.351],
          zoom: 14,
          slider: false 
        });


        map.on("layers-add-result", initEditor);
       
        //add boundaries and place names 
        var labels = new ArcGISTiledMapServiceLayer("http://server.arcgisonline.com/ArcGIS/rest/services/Reference/World_Boundaries_and_Places/MapServer");
        map.addLayer(labels);


        var rivers = new FeatureLayer("http://sampleserver3.arcgisonline.com/ArcGIS/rest/services/Hydrography/Watershed173811/FeatureServer/1",{
          mode: FeatureLayer.MODE_ONDEMAND, 
          outFields: ['*']
        });


        var waterbodies = new FeatureLayer("http://sampleserver3.arcgisonline.com/ArcGIS/rest/services/Hydrography/Watershed173811/FeatureServer/0",{
          mode: FeatureLayer.MODE_ONDEMAND, 
          outFields: ['*']
        });


        map.addLayers([waterbodies,rivers]);


        function initEditor(evt) {
          var templateLayers = arrayUtils.map(evt.layers, function(result){
            return result.layer;
          });
          var templatePicker = new TemplatePicker({
            featureLayers: templateLayers,
            grouping: true,
            rows: "auto",
            columns: 3
          }, "templateDiv");
          templatePicker.startup();


          var layers = arrayUtils.map(evt.layers, function(result) {
            return { featureLayer: result.layer };
          });
          var settings = {
            map: map,
            templatePicker: templatePicker,
            layerInfos: layers,
            toolbarVisible: true,
            createOptions: {
              polylineDrawTools:[ Editor.CREATE_TOOL_FREEHAND_POLYLINE ],
              polygonDrawTools: [ Editor.CREATE_TOOL_FREEHAND_POLYGON,
                Editor.CREATE_TOOL_CIRCLE,
                Editor.CREATE_TOOL_TRIANGLE,
                Editor.CREATE_TOOL_RECTANGLE
              ]
            },
            toolbarOptions: {
              reshapeVisible: true,
              cutVisible: true
            }
          };


          var params = {settings: settings};    
          var myEditor = new Editor(params,'editorDiv');
          //define snapping options
          var symbol = new SimpleMarkerSymbol(
            SimpleMarkerSymbol.STYLE_CROSS, 
            15, 
            new SimpleLineSymbol(
              SimpleLineSymbol.STYLE_SOLID, 
              new Color([255, 0, 0, 0.5]), 
              5
            ), 
            null
          );
          map.enableSnapping({
            snapPointSymbol: symbol,
            tolerance: 20,
            snapKey: keys.ALT
          });
    
          myEditor.startup();
        }
      });
    </script>
  </head>
  <body class="claro">
    <div id="main" data-dojo-type="dijit/layout/BorderContainer" data-dojo-props="design:'headline'" style="height:width:100%;height:100%;">
      <div data-dojo-type="dijit/layout/ContentPane" id="header" data-dojo-props="region:'top'">
        Edit Hydrography
      </div>
      <div data-dojo-type="dijit/layout/ContentPane" data-dojo-props="region:'left'" style="width: 300px;overflow:hidden;">
        <div id="templateDiv"></div>
        <div id="editorDiv"></div>
      </div>
      <div data-dojo-type="dijit/layout/ContentPane" id="map" data-dojo-props="region:'center'"></div>
    </div>
  </body>
</html>

If you can, feel free to move this discussion to another thread and I'll follow it.

Thanks again!

DerivenC

Here's a simple page that creates a polygon and cuts it using the geometry service: http://jsbin.com/UFeCOMUs/1/

Works in Chrome and FF on a mac for me.

Derek,

Thanks for taking a look at this. Unfortunately that's a different use case. Try it with the editor widgit. And if that works, try it with a regular graphics layer or featurelayer collection.

You'll notice that all of the samples from the site do not include the cut tool which I found odd. Why hide it from the main site samples? Especially the editor widget? You have to search for the old sample to see it. And it does not work. (Actually the drawing doesn't work anymore now either. But the cut didn't work for it either in the past.) It's what I mentioned in my original post.

I submitted the bug fix in that email address. Couple of lines fixes the issue. You'll see where the problem is and how I fix it. It is specifically the editor-all file. (Perhaps elsewhere, not certain.)

To the OP, sorry for stealing your thread. 🙂

derekswingley1

Sounds good and completely understand. I'll give the former a try by submitting my bug fix for the Cut polygon issue. As of 3.7, it was still broken.

Here's a simple page that creates a polygon and cuts it using the geometry service: http://jsbin.com/UFeCOMUs/1/

Works in Chrome and FF on a mac for me.

derekswingley1

As an aside, I've sent several emails to that address as far back as July about corrections that should be made to the documentation, such as incorrect code snippets or listed return values. However, the errors still persist.

Sorry about that...can you post links with errors?

DerivenC

Thanks for the additional info. We try to keep a close eye on this forum, but things slip through the cracks. I'm especially curious about that FF-specific issue. We'll look into that.

When you absolutely need an answer, tech support is where you should go. Even if you need to log a bug, support is still the way to go. If that's too much trouble, you can always email js_feedback@esri.com to get our attention.

Sounds good and completely understand. I'll give the former a try by submitting my bug fix for the Cut polygon issue. As of 3.7, it was still broken.

edit: oh yeah, I forgot about the customer number ordeal for the support request. I do not have a customer number or cannot locate it. I'm an independent software vendor and develop for other clients. I guess I could use their customer number. But I suspect that is why some of us do not submit bugs that way -- because we're not the account owners but rather the developers.

I'll try the email approach.

kenbuja

If that's too much trouble, you can always email js_feedback@esri.com to get our attention.

As an aside, I've sent several emails to that address as far back as July about corrections that should be made to the documentation, such as incorrect code snippets or listed return values. However, the errors still persist.

derekswingley1

Thanks for the additional info. We try to keep a close eye on this forum, but things slip through the cracks. I'm especially curious about that FF-specific issue. We'll look into that.

When you absolutely need an answer, tech support is where you should go. Even if you need to log a bug, support is still the way to go. If that's too much trouble, you can always email js_feedback@esri.com to get our attention.

DerivenC

Thanks for testing and confirming 3.8 fixes this issue.

Regarding:

Can you elaborate? Have you logged bugs with support?

Hey Derek,

Appreciate your interest in why I havent. For a couple of reasons really...

1) They've been reported via the forums and ideas sites either by me or someone else. And a couple of the ones that I posted never got a response. I do post my workarounds when it doesn't involve tampering with the API.
2) The "report a bug" site is a "Support Request Form". I personally do not want to request support. I want to submit a bug.

This is not indicating that ESRI ignores the community or anything. I'm fully aware you are all busy and I certainly appreciate the tools you provide us. That is why I don't mind delving into the code and temporarily fixing till you can.

If or when you have a better or direct link to the developers to submit bug fixes, please let me know. What I'd love to see is a public or private git repository that you grant a few of us access (sort of like the beta program). We could help you expedite these bug fixes and improve the API & SDK -- and you choose what you want to accept.

Whew! This certainly went off topic. 🙂

derekswingley1

Thanks for testing and confirming 3.8 fixes this issue.

Regarding:

I have to pull down the SDK/API because there are some bugs I always fix that haven't been fixed yet from ESRI.

Can you elaborate? Have you logged bugs with support?

DerivenC

@benjamin
the download is not available yet, but you can find the hosted version of 3.8 is already available for testing
http://js.arcgis.com/3.8/

Isolated bug test: only testing the scroll-to-zoom bug. Standard map features seemed to work from this initial test.

Tested it on Chrome, Firefox, and Internet Explorer 11 on Windows 7 64-bit with success.
Tested IE10 on Windows Server 2008 R2 with success.

JohnGravois

@benjamin
the download is not available yet, but you can find the hosted version of 3.8 is already available for testing
http://js.arcgis.com/3.8/

DerivenC

We're going to wait until after the new year to announce 3.8. As I said previously, please feel free to upgrade your app (in a development or test environment of course...) and test with 3.8.

As far as what we changed for 3.8, this is a minor release. We still use Dojo 1.9.1 but did upgrade dgrid, put-selector and xstyle.

I would be happy to test it. Is it possible to get the SDK or API download to do the test? I have to pull down the SDK/API because there are some bugs I always fix that haven't been fixed yet from ESRI.

If not, that's okay. I would prefer to do a full test. But I can do an isolated bug test if you would prefer.

edit: tested isolated bug and it works fine in IE11, Chrome, and Firefox desktop version.

derekswingley1

Hi Derek.

We're a bit nervous of upgrading to 3.8 without seeing the documentation which describes the changes. Are you able to advise whether there is anything in this release which changes existing functionality and potentially cause issues? Does it still use Dojo 1.9.1?

If 3.8 fixes the mouse wheel issue with IE11 then I really feel it should be released sooner rather than later.

We're going to wait until after the new year to announce 3.8. As I said previously, please feel free to upgrade your app (in a development or test environment of course...) and test with 3.8.

As far as what we changed for 3.8, this is a minor release. We still use Dojo 1.9.1 but did upgrade dgrid, put-selector and xstyle.

AndrewWillingale

It's still a good idea to test with 3.8. The version on js.arcgis.com is our final build. We're nearly finished with the docs and are debating whether or not to announce before christmas/new year's or hold it until after the new year.

Hi Derek.

We're a bit nervous of upgrading to 3.8 without seeing the documentation which describes the changes. Are you able to advise whether there is anything in this release which changes existing functionality and potentially cause issues? Does it still use Dojo 1.9.1?

If 3.8 fixes the mouse wheel issue with IE11 then I really feel it should be released sooner rather than later.

Thanks,
Andrew.

derekswingley1

It's still a good idea to test with 3.8. The version on js.arcgis.com is our final build. We're nearly finished with the docs and are debating whether or not to announce before christmas/new year's or hold it until after the new year.

AndrewWillingale

No release date yet...can you test with 3.8 and confirm that the IE11 scrolling issue is fixed with that version?

Hi Derek, thanks for your reply. Unfortunately my work place is still on IE8 until we move to Windows 7 next year, so I can't test 3.8. I've only become aware of the IE11 issue from a member of the public.

Cheers,
Andrew.

derekswingley1

No release date yet...can you test with 3.8 and confirm that the IE11 scrolling issue is fixed with that version?

AndrewWillingale

Hi Derek.

Not sure whether you'll see this but do you have a release date for 3.8 please? It looks like it's being hosted already but I don't want to move to it without knowing what may have changed.

Thanks,
Andrew.

kenbuja

Edward,

If Janice's post answered your question (or helped you out), you should click the check mark and/or the up arrow in her post.

You've posted many questions and have received many answers, but you haven't marked any posts (including your own) as having answered your questions. Marking the thread as answered helps others who are looking for answers to these questions in the future. It also rewards the people who help you through the MVP program.

EdwardSohn1

It worked. But it messed up scroll/zooming for firefox. So had to put in browser/version detection for IE11 (for now) as a quick workaround however.

JaniceBaird

I added a function to handle the mouse wheel to correct this problem:


...

dojo.connect(map, "onMouseWheel", mouseWheelHandler);

...

function mouseWheelHandler(evt) {
    var intDelta = evt.wheelDelta;
    try {
        if (intDelta < 0) {
            map.setLevel(map.getLevel() - 1);
        } else {
            map.setLevel(map.getLevel() + 1);
        }
    } catch (exp) { console.debug(exp.Description); }
}

derekswingley1

Easiest way is to change the URL in the script tag that loads the API. Once 3.8 is out, it will be at http://js.arcgis.com/3.8/ (obviously not live yet).

EdwardSohn1

We're aware of the issue but there isn't a workaround.

We have fixed this for the next release of the API (3.8) which will be out in the next two weeks or so.

Sorry if this is a newbie question: but how do you upgrade the API for JavaScript?
I am actually using a customized storytelling swipe template map app.
How would one go about upgrading the underlying API to 3.8?

Thanks.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

All Communities
Recent Posts
Followed Content
Community Help

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.