Closed GoogleCodeExporter closed 9 years ago
Thanks for the report. Which URL are you trying to add?
Original comment by fam....@live.nl
on 16 Feb 2012 at 4:57
I tried a couple. I found Issue 9 and used the URLs posted there (modified
with my address of course), as well as the address I copied from my current
Gmail window: https://mail.google.com/mail/u/1/?shva=1#compose
Original comment by FISHMAN...@gmail.com
on 16 Feb 2012 at 7:01
You probably refer to
"https://mail.google.com/mail/b/his_email@gmail.com/?extsrc=mailto&url=%s"
Which is the FireFox syntax.
As stated below the input box, the syntax supported by this extension is {to}
{cc} {bcc} {body} and {subject}.
These will be replaced by the to, cc, bcc, body and subject of the mailto link.
For this, you need to know the compose URL of the service you want to use. In a
future version, I'll also add a constant {url} which will be equal to %s.
Original comment by fam....@live.nl
on 16 Feb 2012 at 7:44
Ok. I've just added support for {url}.
The URL from issue 9 would be
https://mail.google.com/mail/b/his_email@gmail.com/?extsrc=mailto&url={url}
Does this fit your needs?
Original comment by fam....@live.nl
on 16 Feb 2012 at 8:40
It didn't, but oddly enough that's OK. Because you've added that it suddently
clicked that I have to put those flags into the URL I'm passing the extension.
I assume if I used {url} it would just pass in the entire mailto link?
Part of my problem was also that I have multiple logins enabled, and all those
URLs just revert to the first gmail login. This is the URL I used for my 2nd
(index of 1) account, for anybody that may be helped by it:
https://mail.google.com/mail/u/1/?view=cm&fs=1&tf=1&body={body}&shva=1&to={to}&s
u={subject}&cc={cc}&bcc={bcc}
Original comment by FISHMAN...@gmail.com
on 16 Feb 2012 at 10:07
{url} indeed just inserts the full mailto link, including the protocol.
Is there anything I can still help you with? Or do you have any suggestions how
I could improve the way people can enter those new URLs? Because it sounds like
the issue is fixed for you.
Original comment by fam....@live.nl
on 16 Feb 2012 at 10:51
Now that I understand it I'm not sure why I didn't understand it before. Maybe
have some example URLs to use for the Custom URL field? That probably would
have helped me initially.
Original comment by FISHMAN...@gmail.com
on 16 Feb 2012 at 11:04
Sounds good!
I'll probably do that next week.
Original comment by fam....@live.nl
on 16 Feb 2012 at 11:10
Also, some explanation that you can't click add until the right tags are put
into the URL.
Original comment by FISHMAN...@gmail.com
on 16 Feb 2012 at 11:13
I created AddCustomUrl.
Do you think it contains all the information that someone would need?
If so, I'll add a link to that page in the extension.
I don't add this text in the extension itself, as this would not require me to
push out a new version of the extension every time a small change has been
made. Wiki pages can be updated a lot easier :).
I won't add an explanation why you can't click it in the options page. This is
because all the validation happens in one step, and I would have to split it up
in multiple steps (risking that it could allow more than it should) only to
display a message somewhere.
Original comment by fam....@live.nl
on 22 Feb 2012 at 5:04
Original comment by fam....@live.nl
on 10 Mar 2012 at 1:59
Original issue reported on code.google.com by
FISHMAN...@gmail.com
on 16 Feb 2012 at 4:44