I would like to be able to scroll to the top of the window using an
opensocial call (only allowed on canvas pages). Right now, I can only
scroll to the top of the iframe my app is housed in.
The reason is for situations where I have a long page and a user
changes their page, it stays down at the bottom with their data
showing at the very top. They believe they are at an empty page.
The reason I would like to scroll to the top of the window rather than
the top of the iframe is for cosmetic reasons. It simply looks more
natural, especially on the myspace platform.
Could you give more detail on the sort of page changes occur through an OpenSocial app whose results would show up higher (above-the-fold as it were) on the page?
I'm not convinced that container-mediated page navigation APIs are best suited to the OpenSocial namespace, since they're a pretty generic concept. I wonder if a new feature is a better solution.
On Wed, Apr 9, 2008 at 2:13 AM, Matic <troypa...@gmail.com> wrote:
> Hello,
> I would like to be able to scroll to the top of the window using an > opensocial call (only allowed on canvas pages). Right now, I can only > scroll to the top of the iframe my app is housed in.
> The reason is for situations where I have a long page and a user > changes their page, it stays down at the bottom with their data > showing at the very top. They believe they are at an empty page.
> The reason I would like to scroll to the top of the window rather than > the top of the iframe is for cosmetic reasons. It simply looks more > natural, especially on the myspace platform.
It seems like this would best belong on gadgets.window. Perhaps gadgets.window.scrollToTop = function() {};
We could put this under a new feature called "scrolling" or it could perhaps be put together with one of the other windows methods like dynamic-height. Dynamic height and set title only have one method each as it is, putting them together under an umbrella "window" library or at least starting in that direction might be a good idea.
On Fri, Apr 11, 2008 at 4:55 PM, John Hjelmstad <fa...@google.com> wrote: > Could you give more detail on the sort of page changes occur through an > OpenSocial app whose results would show up higher (above-the-fold as it > were) on the page?
> I'm not convinced that container-mediated page navigation APIs are best > suited to the OpenSocial namespace, since they're a pretty generic concept. > I wonder if a new feature is a better solution.
> John
> On Wed, Apr 9, 2008 at 2:13 AM, Matic <troypa...@gmail.com> wrote:
>> Hello,
>> I would like to be able to scroll to the top of the window using an >> opensocial call (only allowed on canvas pages). Right now, I can only >> scroll to the top of the iframe my app is housed in.
>> The reason is for situations where I have a long page and a user >> changes their page, it stays down at the bottom with their data >> showing at the very top. They believe they are at an empty page.
>> The reason I would like to scroll to the top of the window rather than >> the top of the iframe is for cosmetic reasons. It simply looks more >> natural, especially on the myspace platform.
On Mon, Apr 14, 2008 at 2:30 PM, Cassie <d...@google.com> wrote: > It seems like this would best belong on gadgets.window. Perhaps > gadgets.window.scrollToTop = function() {};
> We could put this under a new feature called "scrolling" or it could > perhaps be put together with one of the other windows methods like > dynamic-height. Dynamic height and set title only have one method each > as it is, putting them together under an umbrella "window" library or > at least starting in that direction might be a good idea.
> - Cassie
> On Fri, Apr 11, 2008 at 4:55 PM, John Hjelmstad <fa...@google.com> wrote: > > Could you give more detail on the sort of page changes occur through an > > OpenSocial app whose results would show up higher (above-the-fold as it > > were) on the page?
> > I'm not convinced that container-mediated page navigation APIs are best > > suited to the OpenSocial namespace, since they're a pretty generic > concept. > > I wonder if a new feature is a better solution.
> > John
> > On Wed, Apr 9, 2008 at 2:13 AM, Matic <troypa...@gmail.com> wrote:
> >> Hello,
> >> I would like to be able to scroll to the top of the window using an > >> opensocial call (only allowed on canvas pages). Right now, I can only > >> scroll to the top of the iframe my app is housed in.
> >> The reason is for situations where I have a long page and a user > >> changes their page, it stays down at the bottom with their data > >> showing at the very top. They believe they are at an empty page.
> >> The reason I would like to scroll to the top of the window rather than > >> the top of the iframe is for cosmetic reasons. It simply looks more > >> natural, especially on the myspace platform.
What's the exact proposal here? Is it just a new scrollToTop() call, or consolidating dynamic height, set title, and scrollToTop function under a new require feature="window" library?
On Thu, Apr 24, 2008 at 9:14 AM, Cassie <d...@google.com> wrote: > Would we like to see this go into the next iteration of the spec? > If so, I need some +1s.
> - Cassie
> On Mon, Apr 14, 2008 at 2:30 PM, Cassie <d...@google.com> wrote:
>> It seems like this would best belong on gadgets.window. Perhaps >> gadgets.window.scrollToTop = function() {};
>> We could put this under a new feature called "scrolling" or it could >> perhaps be put together with one of the other windows methods like >> dynamic-height. Dynamic height and set title only have one method each >> as it is, putting them together under an umbrella "window" library or >> at least starting in that direction might be a good idea.
>> - Cassie
>> On Fri, Apr 11, 2008 at 4:55 PM, John Hjelmstad <fa...@google.com> wrote: >> > Could you give more detail on the sort of page changes occur through an >> > OpenSocial app whose results would show up higher (above-the-fold as it >> > were) on the page?
>> > I'm not convinced that container-mediated page navigation APIs are best >> > suited to the OpenSocial namespace, since they're a pretty generic >> concept. >> > I wonder if a new feature is a better solution.
>> > John
>> > On Wed, Apr 9, 2008 at 2:13 AM, Matic <troypa...@gmail.com> wrote:
>> >> Hello,
>> >> I would like to be able to scroll to the top of the window using an >> >> opensocial call (only allowed on canvas pages). Right now, I can only >> >> scroll to the top of the iframe my app is housed in.
>> >> The reason is for situations where I have a long page and a user >> >> changes their page, it stays down at the bottom with their data >> >> showing at the very top. They believe they are at an empty page.
>> >> The reason I would like to scroll to the top of the window rather than >> >> the top of the iframe is for cosmetic reasons. It simply looks more >> >> natural, especially on the myspace platform.
The proposal is an addition of the scrollToTop function in the windows namespace. If we like that then the second question is which library is belongs in.
To be more clear: 1. Do we add scrollToTop? 2. Where does it go?
My answers: 1. +0, if other people think this is needed than it's fine with me, i don't feel too strongly either way 2. leave setTitle and dynamic-height alone for now. we should put it in a new feature either called "scrolling" or "window". (later we could perhaps migrate dynamic-height and settitle to "window" if we choose the latter)
I hope that helps somewhat.
- Cassie
On Thu, Apr 24, 2008 at 11:02 PM, Arne Roomann-Kurrik <kur...@google.com> wrote:
> What's the exact proposal here? Is it just a new scrollToTop() call, or > consolidating dynamic height, set title, and scrollToTop function under a > new require feature="window" library?
> ~Arne
> On Thu, Apr 24, 2008 at 9:14 AM, Cassie <d...@google.com> wrote:
>> Would we like to see this go into the next iteration of the spec? >> If so, I need some +1s.
>> - Cassie
>> On Mon, Apr 14, 2008 at 2:30 PM, Cassie <d...@google.com> wrote:
>>> It seems like this would best belong on gadgets.window. Perhaps >>> gadgets.window.scrollToTop = function() {};
>>> We could put this under a new feature called "scrolling" or it could >>> perhaps be put together with one of the other windows methods like >>> dynamic-height. Dynamic height and set title only have one method each >>> as it is, putting them together under an umbrella "window" library or >>> at least starting in that direction might be a good idea.
>>> - Cassie
>>> On Fri, Apr 11, 2008 at 4:55 PM, John Hjelmstad <fa...@google.com> >>> wrote: >>> > Could you give more detail on the sort of page changes occur through an >>> > OpenSocial app whose results would show up higher (above-the-fold as it >>> > were) on the page?
>>> > I'm not convinced that container-mediated page navigation APIs are best >>> > suited to the OpenSocial namespace, since they're a pretty generic >>> concept. >>> > I wonder if a new feature is a better solution.
>>> > John
>>> > On Wed, Apr 9, 2008 at 2:13 AM, Matic <troypa...@gmail.com> wrote:
>>> >> Hello,
>>> >> I would like to be able to scroll to the top of the window using an >>> >> opensocial call (only allowed on canvas pages). Right now, I can only >>> >> scroll to the top of the iframe my app is housed in.
>>> >> The reason is for situations where I have a long page and a user >>> >> changes their page, it stays down at the bottom with their data >>> >> showing at the very top. They believe they are at an empty page.
>>> >> The reason I would like to scroll to the top of the window rather than >>> >> the top of the iframe is for cosmetic reasons. It simply looks more >>> >> natural, especially on the myspace platform.
On Tue, Apr 8, 2008 at 5:13 PM, Matic <troypa...@gmail.com> wrote:
> Hello,
> I would like to be able to scroll to the top of the window using an > opensocial call (only allowed on canvas pages). Right now, I can only > scroll to the top of the iframe my app is housed in.
> The reason is for situations where I have a long page and a user > changes their page, it stays down at the bottom with their data > showing at the very top. They believe they are at an empty page.
> The reason I would like to scroll to the top of the window rather than > the top of the iframe is for cosmetic reasons. It simply looks more > natural, especially on the myspace platform.
Considering an Iframe, I can see this as a valid request to provide
functions that overcome these IFrame limitations. But maybe this
should be container specific?
On Apr 25, 10:35 am, "Louis Ryan" <lr...@google.com> wrote:
> Any MySpace folks have feelings on this given that Matic is justifying this
> in part based on experience with that platform?
> On Tue, Apr 8, 2008 at 5:13 PM, Matic <troypa...@gmail.com> wrote:
> > Hello,
> > I would like to be able to scroll to the top of the window using an
> > opensocial call (only allowed on canvas pages). Right now, I can only
> > scroll to the top of the iframe my app is housed in.
> > The reason is for situations where I have a long page and a user
> > changes their page, it stays down at the bottom with their data
> > showing at the very top. They believe they are at an empty page.
> > The reason I would like to scroll to the top of the window rather than
> > the top of the iframe is for cosmetic reasons. It simply looks more
> > natural, especially on the myspace platform.
This thread has not received enough positive approval or consensus for the next spec iteration. It is now closed.
Marco - I highly recommend adding a container specific suggestion like you mentioned. If its usage gets very popular for developers this will be trivial to add to the spec later on. This way, Troy gets what he needs and we can see if this is something all containers need or perhaps is something specific to how myspace does things.
Let me know if there are any problems with this. Thanks.
On Sat, Apr 26, 2008 at 6:44 PM, Marco Ensing <ens...@gmail.com> wrote:
> Considering an Iframe, I can see this as a valid request to provide > functions that overcome these IFrame limitations. But maybe this > should be container specific?
> On Apr 25, 10:35 am, "Louis Ryan" <lr...@google.com> wrote: > > Any MySpace folks have feelings on this given that Matic is justifying > this > > in part based on experience with that platform?
> > On Tue, Apr 8, 2008 at 5:13 PM, Matic <troypa...@gmail.com> wrote:
> > > Hello,
> > > I would like to be able to scroll to the top of the window using an > > > opensocial call (only allowed on canvas pages). Right now, I can only > > > scroll to the top of the iframe my app is housed in.
> > > The reason is for situations where I have a long page and a user > > > changes their page, it stays down at the bottom with their data > > > showing at the very top. They believe they are at an empty page.
> > > The reason I would like to scroll to the top of the window rather than > > > the top of the iframe is for cosmetic reasons. It simply looks more > > > natural, especially on the myspace platform.
|
