Closed GoogleCodeExporter closed 9 years ago
That would be a Chromium bug not a Minimalist bug so you'll have to talk to
them. It's likely a passing bug (Minimalist works most of the time in Canary
but there are versions where it doesn't).
I can't support all versions of Chromium and its derivative products so I only
officially support Chrome Stable, beta, and dev. However the extensions are all
written within the constraints of the Chromium extension framework so any
derivative products that adhere to those standards will be fine.
Original comment by anst...@gmail.com
on 14 May 2011 at 4:06
Issue 261 has been merged into this issue.
Original comment by anst...@gmail.com
on 16 May 2011 at 6:21
Okay, I have posted a question to the Chrome help forum. Maybe it'll turn up
some answers.
http://www.google.com/support/forum/p/Chrome/thread?tid=72e9d6e5dbc10e08&hl=en
Original comment by leopardp...@gmail.com
on 16 May 2011 at 6:36
Tracked down the problem and submitted a bug to Chromium. Star Issue 82784:
http://code.google.com/p/chromium/issues/detail?id=82784
Original comment by anst...@gmail.com
on 16 May 2011 at 4:02
Pushed a workaround because Chromium isn't responding very quickly. Minimalist
will still run on affected builds but the icon will not appear. Change options
from the Chrome Extensions page.
Original comment by anst...@gmail.com
on 18 May 2011 at 4:29
Actually, everything is now working fine, even the icon. Same Chrome version as
before....
Original comment by leopardp...@gmail.com
on 18 May 2011 at 4:43
Really? What version MinGmail are you running and what version Chrome/Chromium
are you running?
If you're not on MinGmail 1.7.29, please update and confirm that the icon still
appears
Original comment by anst...@gmail.com
on 18 May 2011 at 4:46
I had just updated to Minimalist 1.7.29 after your last post, and then
everything worked.
I'm running Chrome 13.0.768.0 Canary, same as I was before you updated it, and
when it wasn't working.
The icon does still appear perfectly, no problems.
Original comment by leopardp...@gmail.com
on 18 May 2011 at 4:48
Crazy. I'm not getting an icon in the same build... But at least it's working
for everyone. I didn't actually change anything. I just put the line of code
that was throwing the permissions error in a try catch block so it doesn't stop
the whole extension from running just because it won't let me display the icon.
Original comment by anst...@gmail.com
on 18 May 2011 at 4:59
Ok well this is odd. I tried re-naming the User Data folder so I could test it
from a clean version. I installed the extension, put in the same settings as I
had had before (with the icon), and it didn't work. Tried it without the icon,
didn't work. So it's not working if I do a fresh install...
Original comment by leopardp...@gmail.com
on 18 May 2011 at 5:11
Well I'm at a loss... I'll keep an eye on it.
Original comment by anst...@gmail.com
on 18 May 2011 at 5:14
Okay, at least it's working on my side (not exactly sure how). Just a thought,
but could it be the fact that my updated version and the fresh install could be
different somehow? Maybe put a fresh version in the Web Store? Who knows...
Original comment by leopardp...@gmail.com
on 18 May 2011 at 5:18
Whenever the Chrome Updates an extension from the Web Store, it overwrites
every local file with the files from the new package even if they haven't
changed. Updated versions are the same as fresh installs except for the
localStorage which is just a couple strings that save your settings. I have no
idea why they would behave differently...
Original comment by anst...@gmail.com
on 18 May 2011 at 5:25
Issue 272 has been merged into this issue.
Original comment by anst...@gmail.com
on 18 May 2011 at 5:28
This is indeed very odd.....in the fresh User Data folder I matched all the
extensions/apps/settings to what I have in the normal one. I even cleared out
all the history/cache/cookies etc. in both. But it still doesn't work at all
with any settings checked in the fresh install.
Original comment by leopardp...@gmail.com
on 18 May 2011 at 5:42
Go to the extensions page, turn on developer mode and open a Gmail tab. Then
click on Background.html under Minimalist for Gmail. In the bottom left of the
pop-up window, click the 2nd icon to open the JavaScript Console. There will
probably be an error there. What is it?
Original comment by anst...@gmail.com
on 18 May 2011 at 5:57
In fact that's exactly what I did before you posted, and sure enough the errors
are different.
The one for Chrome that DOESN'T work is: Uncaught Error: You do not have
permission to use 'tabs.create'. Be sure to declare in your
chrome/ExtensionProcessBindings:199Uncaught manifest what permissions you need.
But the one for the chrome that DOES work is this: ICON NOT LOADING BECAUSE OF
A CHROMIUM BUG. STAR ISSUE 82784: http://goo.gl/XZMSr
Original comment by leopardp...@gmail.com
on 18 May 2011 at 6:01
wtf... the tabs.create method doesn't even require permissions.
see: http://code.google.com/chrome/extensions/tabs.html#method-create
read: "Note: This function can be used without requesting the 'tabs' permission in the manifest."
Original comment by anst...@gmail.com
on 18 May 2011 at 6:08
Again, very odd.
So are you saying you'll just remove that from the manifest and the extension
should work properly?
Original comment by leopardp...@gmail.com
on 18 May 2011 at 6:14
no I actually do need the tabs permission for tabs.onUpdated. I use that method
to detect when Gmail is opened and initialize the page action (URL icon). I
also don't want to edit the manifest because it would require that everyone
re-enable. Last time I had to do that was when I introduced sync and I lost
almost 30,000 active installs because of how bad the system is. The
notification is tiny, easy to miss, and it only appears once. People didn't
know what happened and gave up.
Original comment by anst...@gmail.com
on 18 May 2011 at 6:22
Any thoughts as to why that error appeared?
Original comment by leopardp...@gmail.com
on 18 May 2011 at 6:26
It's a Chromium error in the recognition of the scope of the tabs permission in
extensions. I'm not familiar with the Chromium code so I couldn't tell you
exactly what the problem is but I hope they'll get it fixed soon. It's a
priority 2 bug in Chromium so I'm hoping the next couple weeks.
Original comment by anst...@gmail.com
on 18 May 2011 at 6:34
Ok, well since this is Chrome Canary, it gets updated daily, so that should
help some. I'll post again if I notice any changes.
Original comment by leopardp...@gmail.com
on 18 May 2011 at 6:37
Okay now Minimalist has stopped working completely, still giving the
"tabs.create" error. Now it doesn't work in either version I have.....
Original comment by leopardp...@gmail.com
on 18 May 2011 at 6:51
Damn. Still working on my end but we'll see what it looks like in the morning.
Original comment by anst...@gmail.com
on 18 May 2011 at 7:06
Okay, well as I said in the other post I have Chrome 13.0.769.0 Canary, and
Minimalist (1.7.30) works great now, except now the notification icon isn't
working....
Original comment by leopardp...@gmail.com
on 18 May 2011 at 11:16
the favicon notification icon or the URL icon?
Original comment by anst...@gmail.com
on 18 May 2011 at 11:18
The favicon notification. The URL icon works fine.
Original comment by leopardp...@gmail.com
on 18 May 2011 at 11:21
weird. I'll take a look at it tonight.
Original comment by anst...@gmail.com
on 18 May 2011 at 11:26
Alright, thanks.
Original comment by leopardp...@gmail.com
on 18 May 2011 at 11:27
.......any luck?
Original comment by leopardp...@gmail.com
on 21 May 2011 at 3:13
Oops, sorry I fixed it locally yesterday. Thought I pushed the new copy but
obviously not. Just pushed it.
Original comment by anst...@gmail.com
on 21 May 2011 at 3:38
Oh ok thanks.
Original comment by leopardp...@gmail.com
on 21 May 2011 at 3:50
Gee I'm just great at finding problems, huh?
Well, Custom Buttons isn't working...I made a theme today and wanted the
buttons to go with it but they don't change.
Original comment by leopardp...@gmail.com
on 21 May 2011 at 5:21
I can replicate it in apps mail but it's still working in standard Gmail. Can
you file this bug as a new report?
Original comment by anst...@gmail.com
on 21 May 2011 at 5:28
Sure.
Original comment by leopardp...@gmail.com
on 21 May 2011 at 5:30
Original issue reported on code.google.com by
Asaf...@gmail.com
on 14 May 2011 at 10:13