User Prefs as Widget Title Bug

If you have an input for a user title, like:

<UserPref name="stopname"
default_value="My Metro Stop"
display_name="Stop Name?" />

And the user enters in something like: I'm home &
lovin' it. It gets
displayed as "I&#39;m home &amp;
lovin&#39; it" in the title. It almost
looks like it's not being encoded properly or not decoded
before it
hits the page. But, I'm a little lost on how to fix this
issue. Any
ideas?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Google Homepage API" group.
To post to this group, send email to Google-Homepage-APIgooglegroups.com
To unsubscribe from this group, send email to
Google-Homepage-API-unsubscribegooglegroups.com
For more options, visit this group at ht
tp://groups.google.com/group/Google-Homepage-API
-~----------~----~----~----~------~----~------~--~---

Indeed, I tested this and came up with the same results.
With some further experimentation, all symbols work
(standard windows
keyboard) except for the following:

&     &
'     '
"     "
<     <
>     >
\     the backslash does not produce output, registers as
input (no ???
and fills required fields) and furthermore kills all the
output after
it (perhaps a clue to the problem?)

Hope this helps in searching for a solution.
Goodluck to your problem rprins!

 problem rprins!


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Google Homepage API" group.
To post to this group, send email to Google-Homepage-APIgooglegroups.com
To unsubscribe from this group, send email to
Google-Homepage-API-unsubscribegooglegroups.com
For more options, visit this group at ht
tp://groups.google.com/group/Google-Homepage-API
-~----------~----~----~----~------~----~------~--~---

> &     &
> '     '
> "     "
> <     <
> >     >

Interesting... this was supposed to be a list of the
character, then
character code...

I think the problem is that the input is taking in text in
normal user
input style (like a html form).  When the Gadget accepts the
input, it
breaks it down into HTML formated characters (using the
&; codes).
However, when placing the input back into the title, it is
just
transferring the string's pure contents, and makes no
effort to
translate those contents from HTML code into HTML output.

Sorry if that made no sense (sence, cents?), but I would
wait for good
'ol Ralph to help you on this one.  Chances are tough you
may have to
warn the user not the use the above symbols, or replace
thier code's
within your <script> content (as in do it
yourself...).

Hope this helps.  Post again if you need help with that
replacement
trick.

placement
trick.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Google Homepage API" group.
To post to this group, send email to Google-Homepage-APIgooglegroups.com
To unsubscribe from this group, send email to
Google-Homepage-API-unsubscribegooglegroups.com
For more options, visit this group at ht
tp://groups.google.com/group/Google-Homepage-API
-~----------~----~----~----~------~----~------~--~---

Yea, that's kind of what I expcted. I just wanted to post
to raise
visibility to the API team so that they were aware. But, if
I get a
user who says they see such behavior, I'll inform them that
currently
it is a known issue.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Google Homepage API" group.
To post to this group, send email to Google-Homepage-APIgooglegroups.com
To unsubscribe from this group, send email to
Google-Homepage-API-unsubscribegooglegroups.com
For more options, visit this group at ht
tp://groups.google.com/group/Google-Homepage-API
-~----------~----~----~----~------~----~------~--~---

Sounds like your best course of action at this point.
While your at it, if I've also noticed that you cannot load
a UserPref
variable into the height ModulePref.  It returns an error
something to
the extent of "Unable to load _UP_name into
ModulePref.height since it
is not an integer32".  I was unsure wether they did
this on purpose (to
prevent dynamic height changes of non-inlined modules) or if
its
another bug.  I'd figured I would mention it since it too
has to deal
with the content of UserPrefs (in this case, not being a
32-bit
integer).  Maybe when Google sees yours, they can help me on
this too.

(P.S. rprins) I think I said something wrong up there.  When
I said
replace their code, I meant you could try using
Javascript's
String::replace() method to search the string for the
character code,
replace it with the appropriate symbol, then reload it back
into the
title.  If I remember my tests correctly (you may want to
check
though), every time a user updates their Prefrences (i.e:
clicks the
save button), the Module is reloaded with the new variables.
 So if you
place the script in the API's onloadhandler(), you should
get a
seamless interaction that'd be unnoticable to users.

Good luck in the future, and may Google bless you with it's
good graces



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Google Homepage API" group.
To post to this group, send email to Google-Homepage-APIgooglegroups.com
To unsubscribe from this group, send email to
Google-Homepage-API-unsubscribegooglegroups.com
For more options, visit this group at ht
tp://groups.google.com/group/Google-Homepage-API
-~----------~----~----~----~------~----~------~--~---

Heeyyy, on top of that, i just found something usefull by
accident:
http://www.lookup
tables.com/web.gif
I was looking up ASCII charts for my own question, and I
came across
this.  Maybe it'll help? But if it doesn't that's okay,
took me no time
to find it ;)


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Google Homepage API" group.
To post to this group, send email to Google-Homepage-APIgooglegroups.com
To unsubscribe from this group, send email to
Google-Homepage-API-unsubscribegooglegroups.com
For more options, visit this group at ht
tp://groups.google.com/group/Google-Homepage-API
-~----------~----~----~----~------~----~------~--~---

Hello rprins,

Thanks for the feedback. We are aware of this problem and it
is
currenly escalating in priority.  I will post more info as
it becomes
available.

Regards,
Ralph


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "Google Homepage API" group.
To post to this group, send email to Google-Homepage-APIgooglegroups.com
To unsubscribe from this group, send email to
Google-Homepage-API-unsubscribegooglegroups.com
For more options, visit this group at ht
tp://groups.google.com/group/Google-Homepage-API
-~----------~----~----~----~------~----~------~--~---