W3C home > Mailing lists > Public > public-webplatform@w3.org > July 2014

Re: More compact display for inherited properties and methods in DOM object pages

From: PhistucK <phistuck@gmail.com>
Date: Sun, 27 Jul 2014 21:24:50 +0300
Message-ID: <CABc02_+ZybCt2TB8N9Duqqjnhi7uZNC8-zuCaeFLwy=Kyfnxug@mail.gmail.com>
To: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
Cc: List WebPlatform public <public-webplatform@w3.org>
Right, I missed that.

I have a few (unfortunately, complex) suggestions to this.
- If you are worried about page size, or loading or processing time,
perhaps we could AJAX in the inherited members.
(There is a bug that may be an intended behavior (or simply a limitation, I
am not sure) that you must specify all of the types from which a type
inherits manually, which is inherently bad in my opinion, because of the
manual chaining (which some may be forgotten, or simply not synchronized
when a type inherits from another type suddenly, which happens sometimes)
instead of using data we already have automatically. AJAXing in the content
may be a way to hack support for a single type that gets all of the
inheritance chain)

- If you are worried about a large overwhelming list of members, a display
toggler (like my "more" suggestion) can be used for the inherited members.

Both of these solutions can co-exist, of course.

Having everything from HTMLElement on HTMLDivElement is important, because
you almost really use just HTMLElement, you almost always use some type
that inherits from it. Inexperienced developers usually do not know that
other types exist and sometimes do not understand inheritance, but the
HTMLElement members would definitely be useful for them (className, title,
classList, dataset).
Developers that will visit these pages are usually less experienced ones,
in my opinion, so it makes sense to provide all of the information quickly,
with a simple Control + F to get to anything close to what they need.
(Which is why I prefer not to have a toggler, but it is the lesser evil
than a cloud)

Alternatively, a cloud that expands (on click) to the full list along with
their summaries might be a fair compromise (no navigation, of course).


On Sun, Jul 27, 2014 at 9:13 PM, Amelia Bellamy-Royds <
amelia.bellamy.royds@gmail.com> wrote:

> To clarify:  The "More..." links only affect a few pages *if* we use the
> cloud display for inherited members.  If you want to use non-truncated
> tables to also display the inherited values, that would affect every
> interface that inherits from HTMLElement!
> From this perspective, the cloud display would actually* increase* the
> amount of information available in most pages, because *all* the
> inherited properties/methods would be displayed by name, instead of only
> displaying a small sample of names+summaries.
> On 27 July 2014 11:59, PhistucK <phistuck@gmail.com> wrote:
>  ...
>> Also, If it only affects a couple of pages, I would leave the giant
>> tables in these pages as well. The cloud (and/or title) solution is really
>> bad in my opinion.
Received on Sunday, 27 July 2014 18:25:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:14:07 UTC