04-16-2019 11:00 AM
04-16-2019 11:00 AM
Reading through the info on the various channels, I see this as a notation for the Dev Channel.
"it’s the best build of the week from the Canary channel."
Based upon that tidbit, I was expecting a new Dev build every week. Since we received the first iteration on Monday a week ago, I was expecting an update this past Monday (04/15). Am I reading something incorrectly and setting the wrong expectation?
I have been using Version 188.8.131.52 daily without issue. I am anxious for the spell checking to come to life, or at least the Grammarly extension to begin working before it can be my primary browser in a business environment.
04-16-2019 12:09 PM
@Darrell Shannon I'm not sure about this, but I think what happens is that the Edge team does 7 days of daily builds, and then picks and choose among the feartures/functions to build a weekly Dev build. If that is the right interpretation of Microsoft's language, then I wouldn't expect the new Dev build for a few days after the Edge team has done 7 daily Canary builds. Another poster (in a different thread) said that he believes that Dev builds will be scheduled for Fridays. We'll all know soon enough.
04-16-2019 02:50 PM
@tomscharbach - Thanks for the feedback. We are roughly on the same page. Since the first Dev & Canary build appeared on 4/8, I was anticipating that Canary daily builds for 4/8 thru 4/14 would count as the 7 versions they would select the "best of" from for a new Dev build on 4/15.
Based on the language, I would expect a new Dev build every 7 days, starting from first Dev release on Monday 4/8 but obviously, that is not the case!
04-17-2019 04:31 AM
Hey @Darrell Shannon, you can install the grammarly extension in the new Edge browser. Just follow the steps from here - https://microsoftedgesupport.microsoft.com/hc/en-us/articles/360017581013
I used it while typing this response - correcting a errors :)
04-17-2019 05:37 AM
@Darrell Shannon - am running Canary - Version 184.108.40.206 (Official build) canary (64-bit). However, I quickly tried installing on the dev version as well and it worked there too. Can you try again once - maybe uninstall and re-install. I know it not ideal, it should have just worked.
04-17-2019 05:43 AM
@Darrell Shannon I was wondering that as well.
Further on the download page for Edge, it reads "updated weekly" under Dev channel¹
I would say that is even more setting the expectations than the tidbit you mentioned ;)
I reached out to @MSEdgeDev on twitter, but no response - Oh well, I think we'll get it soon enough, but I agree transparency is needed on the subject :relieved_face:
04-17-2019 09:45 AM
@Darrell Shannon - are you installing Grammarly from Microsoft Edge Insider store (https://microsoftedge.microsoft.com/insider-addons/detail/cnlefmmeadmemmdciolhbnfeacpdfbkd) or from Chrome Web Store?
04-17-2019 10:25 AM
04-17-2019 10:38 AM
@Balaje_Krishnan - Yes. It is the version found in the Microsoft extensions store. The only thing I can imagine at this point is that the problem lies with Edge not yet being able to deal with Active Directory credentials and log-ins. I am logged into the Dev Edge browser with my personal Microsoft account as it will not work with my company domain business credentials. However, the Grammarly account is tied to my business email. As long as there is a valid Grammarly account logged in you would think it would work, but maybe not.
04-18-2019 03:54 AM
@David Elliott Glad to see others have not been updated from 220.127.116.11 like myself.
Strange that some have posted thay they have received an update in the Dev. Channel?
I haven't seen those posts, but as far as I know (based on posts from Microsoft employees on the Edge team) the Dev channel has not been updated to date, so I don't know what is going on. @ericlaw (a Microsoft employee on the Microsoft Tech Community) posted this on another thread yesterday, in case you haven't seen it yet: "[T]his first Dev build is a bit special and I believe the plan is that the first weekly update will be skipped. Weekly update cadence should begin soon." I'm looking for an update next week.
As to the choice of Canary or Dev, that's up to you. Canary is on a daily unpdate rhythm, Dev on a weekly. Canary is less stable than Dev, intentionally so. You can expect Canary updates to crash and burn from time to time (a daily build crashed while scrolling last week; that issue was resolved in the next day's build), while Dev builds (which pick and choose from the best of the past week's Canary features/functions, deploying after user and regression testing) are less likely to do so.
It is a matter of testing style. After I understood the inherent stability of Edge Chromium, I decided to make the new browser my daily driver, using it exclusively when I'm in a Windows environment. And for that, I wanted reasonably stable builds, pointing me to Dev. Others enjoy being on the cutting (bleeding?) edge of testing, and don't need/want the stability. If that fits your style, go for it. Its up to you. Every tester is doing a service.
Version 18.104.22.168 (Official build) dev (64-bit)
04-19-2019 05:40 AM
@Balaje_Krishnan - With the new Dev build today, and the notes regarding certain extensions not working when they rely on a Google related log-in, I had hope that was the issue. My Grammarly account was setup to log-in "Using Google" rather than being a standalone email and password. I went ahead and deleted that account (no longer want to use Google for anything anyway) and setup a new account. Once again added Grammarly (from the Microsoft extensions) to the latest Edge Dev. Fingers crossed, but still the same issue. As I type this the green circle is spinning constantly and never resolves as good or bad.
04-19-2019 10:25 AM
@Darrell Shannon Thank you for your patience with our first Dev channel update. As @ericlaw mentioned, we did take our time with the first update. We have since pushed our first update and everyone should have been notified that the update is ready for install. We expect this process to be smoother in the future. As always, let us know how you feel about the job we are doing.
04-26-2019 05:48 AM - edited 04-26-2019 05:50 AM
@cbomtempo - That would seem a reasonable deduction but alas, here it is Friday and no update! So it would seem that weekly or every seven days means nothing in reality.
@Elliot Kirk - No problem with patience. However, clear insight into what we can really expect as far as a schedule for updates would be great. If the intent really is weekly, then a posting here on why the delay and when to actually expect the next update would be great.
Otherwise, we are In-The-Darkers rather than Insiders.
04-26-2019 06:35 AM
@Rahsna Asurac - The update was available bright and early last Friday, so anticipating the same would not be unreasonable. Fairly sure the process is queued up and a bit more automated than waiting on Fred to make it into work in Redmond and press the button.
04-26-2019 10:16 AM
04-26-2019 10:36 AM
@ericlaw - Nope. Just anxious to get my weekly Dev fix. In a production environment, letting Canary flesh out the hiccups first seems the wiser choice.
Thanks for the heads-up on the new Dev though. A quick current version check triggered the update download even though the browser itself was not reflecting its availability.
04-26-2019 10:59 AM
With today's (04/26) update to version 22.214.171.124 of Dev, I was surprised to see that a working spell check was still not included. However, I was greatly pleased to see that the Grammarly extension for Edge started working this morning, even prior to the browser version update. I am presuming that Grammarly must have made a change in the extension that fixed it. So, while it is a mystery as to why it started working, I will certainly take it! A lack of spell check was the only obstacle to a Chrome uninstall and shifting to Edge dev as my primary at work. Long since done in my home environment with old Edge and new.
04-26-2019 11:56 AM
@ericlaw Not really champing at the bit to get new builds, but trying to understand what to expect from weekly builds, so I can plan myself to update the browser and look at the changes.
Based on the last 2 releases I guess it's safe to assume that we'll get a new Dev release every Friday morning PST.