Lol.  That's a glaring hack; you might want to test it across browsers
before deploying it.

In ALL things, strive for ><>,
Chris


2010/2/22 Данил Сомсиков <danilasomsi...@gmail.com>

> I've found a solution that doesn't require any injections to external
> document. You just need to create form element, e. g. input or
> textare, give it invisible absolute horizontal postion (e. g. -10px)
> and when you need to adjust vertical scroll within your gadget
> content, you set it move it vertically to desired scroll position and
> place focus in it. Browser will automatically scroll to make focus
> element "visible".
>
> 22 февраля 2010 г. 8:47 пользователь Данил Сомсиков
> <danilasomsi...@gmail.com> написал:
> > Thank you, Сhris.
> > Unfortunately, adding bot to support scrolling is not suitable
> > solution from user experience point of view.
> > Anyway, thanks again.
> >
> > 2010/2/22 Chris <jesdisci...@gmail.com>:
> >> Hi.  Because your gadget is in an iframe hosted at a different domain
> that
> >> Wave itself, to give your gadget control over the wave's scrollbar you
> need
> >> some JavaScript in the wave itself which will talk with your gadget.
> The
> >> only way I know to achieve this is by a bot (and I'm not sure how to do
> it
> >> exactly).  See these threads:
> >>
> >>
> http://groups.google.com/group/google-wave-api/browse_thread/thread/e655cab80c0d4b8a/bf7f528427157a63?hl=en&lnk=gst
> >>
> >>
> http://groups.google.com/group/google-wave-api/browse_thread/thread/b7c1af7defd410d4/dd749040fde0bc0d?hl=en&lnk=gst
> >>
> >> In ALL things, strive for ><>,
> >> Chris
> >>
> >>
> >> On Sat, Feb 20, 2010 at 10:41 AM, danilsomsikov <
> danilasomsi...@gmail.com>
> >> wrote:
> >>>
> >>> I'm making gadget with dynamic height content, which may be taller
> >>> than screen. Is there a way that I can scroll container blip to ensure
> >>> that certain part of content in my gadget is visible?
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google
> Groups
> >>> "Google Wave API" group.
> >>> To post to this group, send email to google-wave-...@googlegroups.com.
> >>> To unsubscribe from this group, send email to
> >>> google-wave-api+unsubscr...@googlegroups.com<google-wave-api%2bunsubscr...@googlegroups.com>
> .
> >>> For more options, visit this group at
> >>> http://groups.google.com/group/google-wave-api?hl=en.
> >>>
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Google Wave API" group.
> >> To post to this group, send email to google-wave-...@googlegroups.com.
> >> To unsubscribe from this group, send email to
> >> google-wave-api+unsubscr...@googlegroups.com<google-wave-api%2bunsubscr...@googlegroups.com>
> .
> >> For more options, visit this group at
> >> http://groups.google.com/group/google-wave-api?hl=en.
> >>
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Wave API" group.
> To post to this group, send email to google-wave-...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-wave-api+unsubscr...@googlegroups.com<google-wave-api%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-wave-api?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Wave API" group.
To post to this group, send email to google-wave-...@googlegroups.com.
To unsubscribe from this group, send email to 
google-wave-api+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-wave-api?hl=en.

Reply via email to