On Wed, Dec 18, 2013 at 5:14 AM, Ian Hickson i...@hixie.ch wrote:
My conclusion is that it's a tough call, but the current API is probably
the least bad compromise (there's a resounding endorsement, eh?). I'm not
the final decider on this, though; that would be the browser vendors. I
believe
On Tue, Dec 17, 2013 at 8:13 PM, Scott González
scott.gonza...@gmail.com wrote:
jQuery UI uses open(), close().
Yep that was part of Ian's list above. I was just adding items to it.
On Fri, Sep 27, 2013 at 7:15 AM, Ian Hickson i...@hixie.ch wrote:
On Mon, 26 Aug 2013, Ojan Vafai wrote:
IMO, showModalDialog is the legacy broken API we're stuck with. Better
to name the new thing in a way that's self-consistent and consistent
with everything else (i.e. openModal).
I
On Fri, Sep 27, 2013 at 7:15 AM, Ian Hickson i...@hixie.ch wrote:
On Mon, 26 Aug 2013, Matt Falkenhagen wrote:
Changing the static position after layout breaks much assumptions in the
code and would seem to require invasive work across the render tree,
layer tree, possibly painting, etc
On Thu, Aug 22, 2013 at 7:58 AM, Ian Hickson i...@hixie.ch wrote:
On Mon, 22 Apr 2013, Tab Atkins Jr. wrote:
On Mon, Apr 22, 2013 at 12:38 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 22 Apr 2013, Matt Falkenhagen wrote:
3. For centering in the viewport, the spec mandates that the used
When an element goes fullscreen, should the browser try to retain the
layout of the underlying document, e.g., by creating a placeholder for
the element?
With the top layer, it's possible to style the fullscreened element and
::backdrop such that the underlying document is visible. In such a
(resending from correct address)
On Tue, Jul 16, 2013 at 10:18 AM, Takayoshi Kochi (河内 隆仁)
ko...@google.com wrote:
IIUC WebKit uses internally node's language to determine which font to use
to render text,
e.g for Han unification (https://en.wikipedia.org/wiki/Han_unification)
WebKit has to
I'm working on implementing the ::backdrop pseudo-element[1] for top
layer elements such as modal dialog and have some questions.
1. Should ::backdrop have the same properties as a real top layer
element, such as Its containing block is the initial containing block.
and Ancestor elements with
I have some questions about these concepts.
1. For an inert element, what happens on element.click() or
element.dispatchEvent(new Event('click'))? The spec says an inert node is
treated as absent for the purposes of targeting user interaction events [1].
My interpretation is that the element
I've been working on implementing dialog for Blink. Here are some
questions and feedback.
1. Browsers that don't support dialog will show the content by
default, unlike browsers that do. Should the spec be changed to make
dialogs open by default (and use a closed instead of open
attribute)? Or is
The Fullscreen spec says, for an element in the top layer:
If its specified position property is static, it computes to absolute.[1]
I think this is to make top layer elements out of flow. But then shouldn't
position 'relative' also compute to 'absolute'?
[1]
The spec seems unclear on whether a magically aligned element[1] should
follow its anchor when its anchor moves, e.g., by dynamic style changes or
something like CSS animations.
I think we want the element to follow the anchor. If someone does something
like:
dialog.show(anchor)
anchor.style.top
How are cycles with magically aligned[1] elements resolved?
For example, if a and b are dialogs and you do:
a.show(b);
b.show(a);
I think an anchoring cycle can also occur if an element |a| is anchored to
a descendent of an element anchored to |a|.
[1]
Hello,
I'm trying to implement the positioning of dialog in WebKit and am
looking at the UA style sheet for dialog [1]. Is there a reason
position:absolute is used instead of fixed?
According to the spec, a non-anchored dialog is vertically centered in
the viewport by default. It seems this can
14 matches
Mail list logo
