May I suggest a public changelog to go with the releases? Changelogs
are pretty much standard for open source projects — the community
can't help much if we don't know what's been changed and/or fixed.
Also, changelogs help reassure the public that a project is actively
developed and that the developers appreciate the feedback. :)
> May I suggest a public changelog to go with the releases? Changelogs
> are pretty much standard for open source projects — the community
> can't help much if we don't know what's been changed and/or fixed.
> Also, changelogs help reassure the public that a project is actively
> developed and that the developers appreciate the feedback. :)
> On Sep 8, 12:44 am, Google Guide 2 wrote:
> > Hi Group,
> > We've released an update to Google Chrome that fixes many of the
> > issues reported here, including:
> > - the ":%" error
> > - Javascript trouble on Facebook
> > - confirmed security vulnerabilities
> > You should be automatically updated soon, but if you'd like these
> > important fixes now, follow the instructions here:
After I installed the new version of Google Chrome, the "ask where to
save each file before downloading" option is still unchecked by
default, so how will Google respond to the "carpet bombing" exploit in
the future, will Google Chrome have the "ask where to save each file
before downloading" option enabled by default, or is Google going to
stand by the decision of enabling automatic file downloads by default?
> After I installed the new version of Google Chrome, the "ask where to
> save each file before downloading" option is still unchecked by
> default, so how will Google respond to the "carpet bombing" exploit in
> the future, will Google Chrome have the "ask where to save each file
> before downloading" option enabled by default, or is Google going to
> stand by the decision of enabling automatic file downloads by default?
> On Sep 8, 12:44 am, Google Guide 2 wrote:
> > Hi Group,
> > We've released an update to Google Chrome that fixes many of the
> > issues reported here, including:
> > - the ":%" error
> > - Javascript trouble on Facebook
> > - confirmed security vulnerabilities
> > You should be automatically updated soon, but if you'd like these
> > important fixes now, follow the instructions here:
Something in version 149.29 caused my javascript menu to work
incorrectly?? - It is a drop down menu - worked just fine previous to
the new update - with new update - it opens all items in the menu -
instead of it being a drop-down. This menu has not been changed what-
so-ever - and works fine in all other browsers - as well as worked in
Chrome up until this last update. I am hoping I am not alone and
hopefully this is an easy fix? My Web Site is http://www.mfllive.com
@GJ6Kings: Dunno what's causing the problem, but it seems Chrome is
detecting an error in your Javascript. Go to Chrome's Javascript
console (page icon > Developer > Javascript console) to see what I
mean.
> Something in version 149.29 caused my javascript menu to work
> incorrectly?? - It is a drop down menu - worked just fine previous to
> the new update - with new update - it opens all items in the menu -
> instead of it being a drop-down. This menu has not been changed what-
> so-ever - and works fine in all other browsers - as well as worked in
> Chrome up until this last update. I am hoping I am not alone and
> hopefully this is an easy fix? My Web Site ishttp://www.mfllive.com
> On Sep 7, 9:44 am, Google Guide 2 wrote:
> > Hi Group,
> > We've released an update to Google Chrome that fixes many of the
> > issues reported here, including:
> > - the ":%" error
> > - Javascript trouble on Facebook
> > - confirmed security vulnerabilities
> > You should be automatically updated soon, but if you'd like these
> > important fixes now, follow the instructions here:
It's a BETA, people. And unlike most Google products, this one
actually qualifies as a BETA!
Heck, just trying to access the Options window crashes the browser.
Doesn't surprise me that it has some flaws this early in it's Beta
cycle.
> After I installed the new version of Google Chrome, the "ask where to
> save each file before downloading" option is still unchecked by
> default, so how will Google respond to the "carpet bombing" exploit in
> the future, will Google Chrome have the "ask where to save each file
> before downloading" option enabled by default, or is Google going to
> stand by the decision of enabling automatic file downloads by default?
> On Sep 8, 12:44 am, Google Guide 2 wrote:
> > Hi Group,
> > We've released an update to Google Chrome that fixes many of the
> > issues reported here, including:
> > - the ":%" error
> > - Javascript trouble on Facebook
> > - confirmed security vulnerabilities
> > You should be automatically updated soon, but if you'd like these
> > important fixes now, follow the instructions here:
> After I installed the new version of Google Chrome, the "ask where to
> save each file before downloading" option is still unchecked by
> default, so how will Google respond to the "carpet bombing" exploit in
> the future, will Google Chrome have the "ask where to save each file
> before downloading" option enabled by default, or is Google going to
> stand by the decision of enabling automatic file downloads by default?
Change the default Downloads directory if it is set to Desktop,
and ensure that Desktop cannot be the default. This mitigates the
risk of
malicious cluttering of the desktop with unwanted downloads, which
can
lead to executing unwanted files.
so instead of enabling "ask where to save each file before
downloading" by default, it changes the default download directory?
(somehow Chrome never set default download directory to desktop for
me)
But that still can lead to malicious website littering the download
directory with unwanted download, albeit it may not lead the automatic
execution...
> > After I installed the new version of Google Chrome, the "ask where to
> > save each file before downloading" option is still unchecked by
> > default, so how will Google respond to the "carpet bombing" exploit in
> > the future, will Google Chrome have the "ask where to save each file
> > before downloading" option enabled by default, or is Google going to
> > stand by the decision of enabling automatic file downloads by default?
> Change the default Downloads directory if it is set to Desktop,
> and ensure that Desktop cannot be the default. This mitigates the
> risk of
> malicious cluttering of the desktop with unwanted downloads, which
> can
> lead to executing unwanted files.
> so instead of enabling "ask where to save each file before
> downloading" by default, it changes the default download directory?
> (somehow Chrome never set default download directory to desktop for
> me)
Because default download directory wasn't Desktop. It was My
Documents/Downloads. (unless your IE or FF's download directory was
Desktop and you imported settings from them.)
> But that still can lead to malicious website littering the download
> directory with unwanted download, albeit it may not lead the automatic
> execution...
I guess Google thinks its not too risky with phishing and malware
protection enabled by default.
I just followed the link you referenced, and the tools 'About chrome'
reported that version 149.29 is installed, but I continue to encounter
the same issues re facebook , namely that Chrome does not recognise
any action links eg changing profile settings, editing notes, rating
movies etc etc etc ... so currently (ie v149.29) Chrome looks sleek
but is useless if I want to use facebook when I am online ...
It would be nice if we were *told* that our version of the software
had been updated, instead of having it happen invisibly. I wouldn't
have known if I hadn't seen it here.
Did Chrome update automatically for you? It didn't for me. I had to
check for updates in the "About Google Chrome" section, then I had to
click the "Update Now" button for it to update. Nothing automatic,
though I suppose it is possible that I checked for an update before
Chrome did its own regular checks.
> It would be nice if we were *told* that our version of the software
> had been updated, instead of having it happen invisibly. I wouldn't
> have known if I hadn't seen it here.
