By Guy Goodall on Thursday, 10 December 2015
Posted in General Issues
Replies 11
Likes 0
Views 1K
Votes 0
Hi guys,

Although this might not qualify as a huge bug it's nonetheless a little one and quite annoying. Especially if you're a Microsoft Edge user and I rather suspect there's quite a "few million" of users out there.

Anyhow, here's what to do to see the issue:

Go to your demo site using MS Edge.
Now go to EasyBlog - scroll up - down using keyboard arrows - OK
Do the same for EasyDiscuss and komento - OK too.

Now go to EasySocial and try scrolling up - down using keyboard arrows - Not OK. Wont scroll or if functions poorly. So obviously something in EasySocial coding causing this as it works fine in three other products.

Now that you know, hope you can fix it for the sake of us who like to use our arrow keys when browsing, making using EasySocial a pleasure to use .

Cheers!
Hey Guy,

It's actually a long weekend off for most of us here and I don't have a windows machine (Trying to setup one now with Parallels vm). Does this problem still occur for you with the latest EasySocial version? I believe we have already resolved several "touch" events but because our demo is not running off the latest version, I am not sure if this is why you are still experiencing similar issues on our demo.
·
Friday, 11 December 2015 15:19
·
0 Likes
·
0 Votes
·
0 Comments
·
Mark,
I've just had a look at v1.4.5 and Edge.

This is what happens.
Enter my site and can use arrow keys OK to start with. Hit an internal link, lets say Archives or other then it's crippled - can't use arrow keys. Refresh page and usually can use arrow keys, but this seems to be erratic.

I hope this helps and go enjoy your long weekend

/Guy
·
Friday, 11 December 2015 15:37
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Guy,

Just tried this on your site with Windows 10 + Edge but can't seem to reproduce this issue After clicking on a link on the sidebar, the arrow keys are still working fine. (Not sure if this is because I am using Parallels VM)
·
Friday, 11 December 2015 17:59
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark,
I don't know either, but I guess so. Unfortunately, there's nothing like the real thing.

Have you not thought of getting a cheap laptop with Windows 10, Edge and IE 11 pre-installed? A pretty useful tool of your trade I would have thought?

I'm unable to verify if this issue happens on another PC running Windows 10 and Edge as I don't have one available at the moment. In other words if the issue is unique to my hardware.
I would be most surprised if it was though
·
Sunday, 13 December 2015 13:02
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey guy,

I will get one of my colleagues to test this (He has a windows 10 and edge machine installed). I think Parallels does a pretty good job and it would be a no brainer for me to purchase another windows machine just to test issues like this because the environment on Parallels should be exactly the same as a normal Windows 10 laptop.
·
Sunday, 13 December 2015 15:38
·
0 Likes
·
0 Votes
·
0 Comments
·
Mark
In my profession as Webmaster and through many years of practical experience you cannot rely on simulations in place of the real thing. They are never 100%
Logically speaking how do you know it's not a combination of your hardware and Parallels causing a difference from what you experience and what I experience? And yep, your colleague might be able to provide an answer?

I can't say conclusively if it's just a one off and my PC and software only. But I'll stick my neck out and say I do not believe it is.

You'd be much closer and of course much more efficient if you could have returned an answer from the onstart for example:

"Yes, my colleagues and I all running Windows machines and software have not been able to reproduce this situation. Therefore, we'll need to consider if it's possibly something to do with your local environment?"

For me, that's a no brainer

Cheers!
·
Sunday, 13 December 2015 16:58
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Guy,

I am really sorry for the delay of this reply.

I've tested this issue with my windows 10 machine Dell Inspiron 7000 series with Edge browser and it seems like the scrolling is working correctly when I press key up and down using my keyboard. Refer my video link here where I've added the keyboard input listener and output it inside the console for a better view, http://screencast.com/t/bLsNbLUey3A .

Perhaps you can try to use other windows machine that available on your side and see if the outcome is still the same.
·
Monday, 14 December 2015 11:44
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks

As I said I don't have access to another machine at present. This is not a high priority issue.
it's become time consuming and mildly annoying. I've posted quite a few tickets about IE 11 and Edge incompatibilities and in the vast majority you guys have not been able to replicate them, at least at first.
Then later on, someone on the support team actually does manage to replicate it - but not all of you that may be dealing with the ticket at the time.

I'm running my tests and observations on a brand new HP laptop with factory installed Windows 10, IE 11, Edge etc.
There are no problems scrolling, EasyBlog or EasyDiscuss. It happens only in EasySocial.

Anyway, just think, could it really be my machine and software?

I don't think so, but I cannot rule it out altogether as I've pointed out before.

You're asking if I can test it on another machine my end which I agree would be a good idea if I had one. I do not at the moment.

However here's what I can do.

I think the following solution will be more effective, less time consuming and a lot less frustrating in the long term

As I'm actually getting some amazing video software for Christmas I'll compile a video with the bugs I'm experiencing.

Then I'll Post it to YouTube and others... and measure the response from a worldwide and willing public.

I'm guessing from all the millions out there they'll be a segment that'll be willing to help out don't you think

Cheers!
·
Monday, 14 December 2015 17:05
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Guy,

Thank you for your kind response and suggestion. To be honest we do not like to accept the fact that we are not able to replicate the issue either as we have might have missed something when we are trying to replicate it directly from our local machine. We will keep trying and hopefully we will able to replicate it and provide you with the necessary fix in the future.

Thanks for understanding.
·
Tuesday, 15 December 2015 19:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Ezrul,

Yes I know that, and I believe you're doing your best. Absolutely no problems with that

I don't wish to cause any extra work as like you guys I'm busy too. Anyway, let me know what you come up with if anything.

Oh yes, I observed from your video you had the console panel open. I did the same and got an error message as you'll see from the screen dump. Is it possible to fix this?

Cheers!
·
Tuesday, 15 December 2015 19:36
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Guy,

Seems like the stylesheet is no longer being use in elegant templates but the index file is still calling it. I've fix this by commenting out the following code inside your /templates/elegant/index.php and it should no longer showing any error now.
<link type="text/css" rel="stylesheet" href="<?php echo TEMPLATE_URI;?>/icons/material/css/material-design-iconic-font.min.css" rel="stylesheet"/>


I will forward this to our elegant template designer so they can include this fix in the next version release of elegant template.
·
Wednesday, 16 December 2015 16:04
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post