Posts

Whilst fully understanding Nigel’s advice regarding the wisdom of upgrading to Windows 10 too early in it’s life, as I have a number of users of my site who have already done so and I know that at least some of them are using the new browser “Edge” (which, as Nigel has said, can only be used under W10), I have taken the plunge and upgraded both my desktop and a laptop to Windows 10 to check it out, and have tried using kiwitrees with the Edge browser and thought it may be useful to report my findings to the forum. I can report that, in general, it was perfectly OK; so much so that I had to check from time to time to be sure that I was in Edge and not in Chrome.

However one problem emerged which although not a major issue is a very irritating one. When you hover the cursor over any point on the page that has a link, Edge, like other browsers, shows the full url (link title) somewhere on the screen. Like my preferred browser Chrome, Edge chooses to place this in the extreme bottom left of the screen – sufficiently out-of.-the-way to cause no problem. However, unlike Chrome (not sure about other browsers?), Edge also chooses to do this in pop-up windows, so having completed a change in the Edit pop-up window in kiwitrees, and you move the cursor down to the bottom left corner of the window to click the ‘Save’ button, you can’t see the button because it’s covered with the link title – which wouldn’t be so bad if it appeared as a clickable hyperlink but of course it doesn’t. So the frustrating challenge is to move the cursor quickly back and forth to try to touch the button before it’s covered again!

Personally, I think it’s a deisgn error in Edge because displaying the link title inside a relatively small window is almost guaranteed to hide something important, wherever it is placed. So maybe it will be ‘fixed’ in the near future by Microsoft, but …. we’ve thought that about things before with MS and been disappointed.

Of course, if Nigels’s thoughts about replacing pop-up windows were to be implemented, the problem would go away. The only alternatives that I can see, if MS don’t change Edge, are either for kiwitrees users to avoid Edge, or for the ‘Save’ button in the kiwitrees pop-up window to be shifted to the right and grouped with ‘Check’ and ‘Close’.

Ron in France Website: https://clan-davies.kiwitrees.net/ kiwitrees 3.3.11; PHP 8.0.14

clandav wrote:

Of course, if Nigels’s thoughts about replacing pop-up windows were to be implemented, the problem would go away. The only alternatives that I can see, if MS don’t change Edge, are either for kiwitrees users to avoid Edge, or for the ‘Save’ button in the kiwitrees pop-up window to be shifted to the right and grouped with ‘Check’ and ‘Close’.

Well, I decided over the Christmas break that MS had probably fixed enough of the Windows 10 bugs now, so I could risk going through the upgrade process. To be fair, I did upgrade one inconsequential machine a couple of months ago and tested my mission-critical development tools on that.

Not being a great fan of MS it pains me to report that all went amazingly smoothly! Apart from the long download, the upgrade took only an hour or so. I’m now up and running again with everything exactly as I like it. No issues (that I know of so far) of any concern.

As Ron said, the MS Edge problem of the status bar obscuring the Save button is a non-issue on the new full-page / tab edit screens.

Nigel
My personal kiwitrees site is www.our-families.info

I have been running Windows 10 for some time and concur that Edge doesn’t play well with kiwitrees primarily for the reason clandav stated. IE11 is also included with Windows 10 and plays a bit better, however, it has an aggravating habit of not working well with the kiwitrees logon link.

For a number of reasons, I am not a fan of Chrome and have explored some other options to use. By far the browser that seems to play the best with kiwitrees is the latest version of Firefox. I don’t think it opens the pages as fast but there certainly is a lot less aggravation using it.

Roy

Roy

Apache 2.4.27  PHP 7.19 MariaDB 10.2.8

Roy wrote:

concur that Edge doesn’t play well with kiwitrees primarily for the reason clandav stated

As noted above, that particular problem disappears with the next release of kiwitrees. But if you find any other issues with Edge please let me know asap.

Browser choice is a very personal one. I, for example, am a fervent Chrome fan. I find FF tolerable, but most others I avoid at all costs, other than necessary development testing.

Nigel
My personal kiwitrees site is www.our-families.info