Scheduler Version: v.3.3.11
IE Version: 11.666 or Emulator IE11 windows 8.1 Update
Windows: 10
Jquery Version: 1.5
I'm trying to display lightbox when drag ends but it's not working on IE specific version but it works on all other browsers and other IE browser versions.
I tried binding with onDragEnd & onBeforeEventChanged, but both events are not getting triggered
But when I target IE browser to IE 9 everything, works fine , don't know what is causing the issue
Code as follow :
scheduler.attachEvent("onDragEnd", function(id, mode, e){
console.log(id);
scheduler.showLightbox(id);
});
scheduler.attachEvent("onBeforeEventChanged", function (event_object, native_event, is_new, original) {
scheduler.showLightbox(event_object.event_pid);
});
when i run this code block from console directly
scheduler.showLightbox(12235654);
lightbox gets dispalyed
I'm not sure that this issue can be solved in another way, except for installing a different version of IE. Since this is a very specific problem that is related to the browser version and not to DHTMLX Scheduler events.
Related
There is an issue with the hover effect that only appears on Safari 10.0.
The web is this:
Manu Caballero
What is happening is that the effect is working radomly, or not working at all:
To see it working, you can use Chrome or Firefox.
The most strange thing is that, on Safari 10.0, if I try to use the inspector, the hover effect works...
On Safari 10.1 and other common browsers like Chrome, Firefox... is working perfectly.
Looking at this site it appears to be using jQuery 1.12.4 and jQuery Migrate 1.4.1 - this is adequate if you need to support IE6 but not something I'd expect to be sufficient for Safari 10 (released after these legacy libraries).
On top of this you appear to be using Isotope 3.0.1, which is also about a year out of date.
So, first I'd recommend:
Upgrading to a current version of jQuery and dropping Migrate - IE6 is dead and IE8 is marginal.
Upgrade Isotope to the current version.
In particular check their issue logs for similar issues before raising them on here.
If the problem persists after that then you may have an issue specific to your implementation. Isolate the code in a snippet in your question - it's much easier for us to help you with one specific issue without reverse engineering your entire site.
Delete this code https://yadi.sk/d/YmKdx2Rd3M2Fcj and your effect will be work fine
and look this video https://www.screenmailer.com/v/EEa7t15khxyLE9s
The software(developed in dojo) I am working on has the feature of drag and drop, things were working fine on all the browsers, just recently our QA team informed me that the drag and drop feature of out product is not working on Windows 10 IE11 only, all the other browsers even including IE11 on windows 7 and 8 support drag and drop feature in our product.
I suppose this could be due to an update that got applied to the Windows 10 installation, since the QA mentioned that this feature was working on Windows 10 IE11 a few months back.
So I tried the following example on both the browsers and noticed that it failed on Windows 10 IE11 only
http://sitepen.github.io/sp-dnd-demo/4-dnd.html
Currently I am trying to debug the dojo code for Manager.js and Source.js
Till now I noticed that in Source.js the drag event is getting executed correctly but the target is getting cleared hence the onDrop event is not getting called
The dojo used is latest 1.10
Please provide me any pointers on resolving this issue
Thanks
I was working upon a website with a flipbook kind of jQuery effect provided by turn.js.
It was working very well on my development environment. Suddenly have found out that the mouseover effect and mouseclick has stopped working on browser Chrome V29.0.1547.66m.
It works perfectly with V26.0.1410.63 and on other browsers (Firefox).
Need to know the reason and some workaround solution for the same.
Here is the link to my webpage.
I had checked your link, I think there is some problem in turn.min.js script. Use turn.js script in place of turn.min.js it is working fine on your link.
As per issue no 399 posted on blasten/github https://github.com/blasten/turn.js/issues/399 change your turn.min.js to latest version of turn.js. This will surely solve your issue with chrome browsers' latest version on windows.
helloi was using the unminified version of turnjs and still had problems with some browsers, i read the code and discovered that mouse move events were not dispatched
i tested with 2 computers :
old Toshiba laptop with 1st-gen i7, Windows 7 Pro SP1, Opera 35.0.2066.68, Firefox 44.0.2 64Bits
brand new Intel NUC5i7RYH, Windows 8.1 Pro, same browser versions
mouse events
working properly on NUC + Firefox and Toshiba + Opera
NOT working on NUC + Opera and Toshiba + Firefox
uh ?
mouse || touch callbacks are set at line 28
touch capacity is detected at line 26
the isTouch test at line 26 returns true on some desktop browsers, which causes the mouse controls not to work
i noticed many tests provided on forum an blog posts didn't detect touch capacity properly, because they often check if touch APIs exist, which seems to be true in some Opera and Firefox browsers (i read some posts about people having the same problem with Chrome, mine works well)
i ended up using this test, which is far from perfect but does the job for now :
!(window.screenX != 0) && ('ontouchstart' in window || 'onmsgesturechange' in window);
i have no more problems, but this solution should be tested on many devices and the isTouch test must be improved
also, i got a bug in the zoom (line 90) while using latest version of jQuery, which i fixed by unchaining the two listeners as follows :
this.mousedown(zoomMethods._mousedown); // what ? chaining bug ?
this.click(zoomMethods._tap);
I have one of those issues that I have been staring at and researching, but can't figure out.
I am loading a listing page with a hash: (example URL)
service_page1.php?u=XX01-TR000016#000016
I have my anchors set: (Example Code)
<div class="b_list_normal_row_ws">
<a name="000013"></a>
<div class="b_list_row_item_But"><img example />
</div>
</div>
Currently I am testing within Safari (latest version) on a Mac. When I load the page, it scrolls to the proper spot for the anchor and then scrolls to the top. I have read other threads about stopping the auto-scroll to the top, but not found one (as of yet) that solves my problem.
Update: I have been working to figure out what could be causing this issue. I have since discovered that if I remove ALL included js files, then the anchors work just fine. However, if I include even the jquery file, then they stop working. The search continues...
Upon serious amounts of testing, it turns out that Safari (6.0.4) is the cause of the problem.
Tested with different browsers, Safari is the only one that is having the problem with the anchors.
With Safari, there is some form of conflict between javascript and the anchors, though it is out of my control. I have updated all my scripts to the latest versions also.
Browsers tested, all the latest possible versions:
Safari (Windows)
Firefox (Windows)
Chrome (Windows)
IE 9
Firefox (OS X Latest)
Chrome (OS X Latest)
Safari (iOS)
Chrome (iOS)
Safari (OS X Latest)* The problem child
UPDATE (June 11):
I have just tested the same site with the new version of OS X and Safari in the public preview and it seems that they fix this issue with the next release. Hopefully, they don't break it again before then.
I have the below site:
http://kelseydelo.com/
When I click the main nav links in Safari the content slides properly. However in Chrome and Firefox nothing happens when I click these (no errors in Firebug either).
I believe it used to work in FF so it seems a recent upgrade has broken it.
Anyone know what the problem could be?
you use mootools 1.2.3 which is old. in 1.2.3, mootools utlised feature detection for browser detection - and in particular, it was a problem with firefox as it relied on the following code:
if (!document.getBoxObjectFor ...)
but that method got made obsolete by mozilla. subsequently, in 1.2.5 and 1.3 mootools detection was done so it does not rely on this any more (breaking change was FF 3.6.nn or something)
on your site in FF 4.0 you can run
console.log(Browser.Engine)
and it comes back as 'unknown' - which will make any browser-specific hooks and fixes fail.
In Chrome 13 Canary, it detected webkit fine but does not work either so there must be something else -- legacy here... in other words, UPGRADE to 1.3.2 (which uses ua-sniffing) - if noobslide supports it, else go 1.2.5.1