ReadyNASOS 6.1.6 [RC13], no frontview in Chrome

[Nessi]

After today's update of Chrome (34.0.1809.0) frontview can no longer be opened.
It appears only the background picture but no settings.
On a second PC with Chrome before the update (34.0.1797.2) it worked.
After the update, frontview does not work.
Firefox and IE continue are still OK.

[vandermerwe]

I've just checked Chrome version as Version 32.0.1700.102 and it states that it's up to date.
This is the most recent stable release of chrome as far as I can see.

You have installed a Dev channel update of chrome - intentional?

OS 6 interface displays normally on the version I have

[Grievous]

32.0.1700.102 is the current stable release, rarely would we consider supporting the beta channel, certainly not the dev channel.

[vandermerwe]

That's essentially what was implied in my message.

[Grievous]

vandermerwe wrote:
That's essentially what was implied in my message.

Right, but I'm not implying it.

[Nessi]

I agree, it’s not a problem, it was just a hint.
So let's wait until Google distribute the “feature” with the next official release.
If all chrome user run into the problem then, no hurry to fix it 😉

[garyaj]

Still not working with Chrome version 34.0.1847.11 beta.

[Grievous]

garyaj wrote:
Still not working with Chrome version 34.0.1847.11 beta.

Stop using the chrome dev and beta channels.

[gclyn]

Same here, exact same problem, unable to get into my NAS using chrome. I can with IE or Safari. Weird. There is a new update, 6.1.7 out now. I've had nothing but problems since updating to 6.1.6

[mdgm-ntgr]

Chrome 34 recently went stable. This is a known issue and one would expect compatibility will be addressed in a future release.

[adamofgreyskull]

Nessi wrote:
I agree, it’s not a problem, it was just a hint. So let's wait until Google distribute the “feature” with the next official release. If all chrome user run into the problem then, no hurry to fix it 😉

THIS!

v34 is now stable branch so what will be the excuse for not fixing it now?

[mdgm-ntgr]

One would think most likely it would be fixed in the next release.

[CharlesR]

mdgm wrote:
One would think most likely it would be fixed in the next release.

One would have hoped it was resolved in the current release since it had been previously reported.

[mdgm-ntgr]

Chrome 34 went stable late enough in the development of 6.1.7 that they clearly didn't see it as critical enough to delay the 6.1.7 release. There were security issues such as Heartbleed which needed urgent addressing.

[CharlesR]

mdgm wrote:
Chrome 34 went stable late enough in the development of 6.1.7 that they clearly didn't see it as critical enough to delay the 6.1.7 release. There were security issues such as Heartbleed which needed urgent addressing.

I agree about the security. I came very late to the 6.1.7 Beta and it seems like it was in Beta for quite a while. That's why I'm surprised it wasn't included... one knows the updated Chrome was going live at some point... Admittedly there isn't much to do once configured and if I just didn't just place a couple online I wouldn't have even bother to complain. 🙂

[Skywalker]

6.1.8-RC1 is available now, which works with Chrome 34. The issue is apparently a XML parsing bug in Chrome 34 that is actually already fixed in Chrome 35 beta.

[CharlesR]

Thanks! Off to download it now...

[williamyzfr1]

Skywalker wrote:
6.1.8-RC1 is available now, which works with Chrome 34. The issue is apparently a XML parsing bug in Chrome 34 that is actually already fixed in Chrome 35 beta.

.

Thanks, fixed my Chrome problems and my IE11 "Device Busy/Not ready" messages. 😄

[Roel1]

Thanks Skywalker. I've just upgrade to Chrome 35 beta and I can now access Frontview again.