:
> On Tue, 27 Sep 2011, Kaustubh Atrawalkar wrote:
> >
> > A simple use case -
> >
> >
> >
> >
>
> (Note: This isn't a "use case", it's a sample. A use case is a description
> of the reason why an author or user wants to do some
?id=47182. I will link this thread
there for fixing the same.
- Kaustubh
On Wed, Feb 22, 2012 at 10:57 AM, Ian Hickson wrote:
> On Sat, 8 Oct 2011, Kaustubh Atrawalkar wrote:
> >
> > In a form element, If a form input element has a focus and its then made
> > hidden
Reopening discussion. Just curious about what can be exact behavior expected
in this case?
I have attached the sample use case.
- Kaustubh
On Tue, Sep 27, 2011 at 11:35 PM, Kaustubh Atrawalkar wrote:
> A simple use case -
>
>
>
>
> This does not submit the form in IE, Oper
On Mon, Sep 26, 2011 at 2:36 AM, Glenn Maynard wrote:
> On Sun, Sep 25, 2011 at 1:02 PM, Ryosuke Niwa wrote:
>
>> The current Trident/WebKit behavior has a nice side-effect to (without
>> scripts) require a visible submit button to enable implicit form submission.
>>
>
> I don't find that nice.
for consistency? Any comments would be great.
Thanks & Regards
--
Kaustubh Atrawalkar
On Mon, Sep 26, 2011 at 2:36 AM, Glenn Maynard wrote:
> On Sun, Sep 25, 2011 at 1:02 PM, Ryosuke Niwa wrote:
>
>> The current Trident/WebKit behavior has a nice side-effect to (without
>> scripts) require a visible submit button to enable implicit form submission.
>>
>
> I don't find that nice.
be the exact behavior
here?
According to specs, (
http://www.whatwg.org/specs/web-apps/current-work/multipage/number-state.html#submit-button-state)
when button is activated, it should submit the form.
--
Kaustubh Atrawalkar
>
> Right. The question is whether read-only/disabled/hidden inputs should be
focusable.
>>>
>>> Readonly elements are focusable both in IE and WebKit.
>>>
>>
>> Agree, then they can be autofocus-able as well as per algorithm.
>>
>
> No, I don't necessarily conclude that. Backward compat
On Sun, Sep 25, 2011 at 10:10 PM, Ryosuke Niwa wrote:
> On Sat, Sep 24, 2011 at 11:06 PM, Kaustubh Atrawalkar <
> kaust...@motorola.com> wrote:
>>
>> My perspective would be absence of submit button (with either
>> visibility:hidden OR display:none) would giv
On Sat, Sep 24, 2011 at 9:38 PM, Ryosuke Niwa wrote:
> On Fri, Sep 23, 2011 at 1:27 PM, Ojan Vafai wrote:
>
>> On Fri, Sep 23, 2011 at 11:49 AM, Ian Hickson wrote:
>> > > There are no as such concrete use cases though, one use case can be if
>> > > user want to get the element in focus (may be
On Sun, Sep 25, 2011 at 5:25 AM, Glenn Maynard wrote:
> On Fri, Sep 23, 2011 at 2:52 PM, Ian Hickson wrote:
> > The strict answer is that it's up to the browsers; the spec allows
> > browsers to do whatever they think is appropriate per their platform's
> > conventions. So both behaviours are co
On Sat, Sep 24, 2011 at 1:57 AM, Ojan Vafai wrote:
> On Fri, Sep 23, 2011 at 11:49 AM, Ian Hickson wrote:
>
>> On Fri, 23 Sep 2011, Kaustubh Atrawalkar wrote:
>> >
>> > Reference -
>> > http://www.whatwg.org/specs/web-apps/current-work/#attr-fe-autofocus
>
> >
> > If the form has submit button with display property as none, will that
> > form should be implicitly submitted on pressing enter key? This works in
> > Opera & Firefox but does not work in IE & Safari as of now. What is the
> > expected behavior for this?
>
> The strict answer is that it'
works in Opera &
Firefox but does not work in IE & Safari as of now. What is the expected
behavior for this?
Thanks & Regards
- Kaustubh Atrawalkar
if user
want to get the element in focus (may be by scrolling the page on load).
Currently, Firefox & Opera does focus the readonly elements on autofocus
whereas IE & Webkit does not. Need to clear the ambiguity.
Thanks & Regards
--
Kaustubh Atrawalkar
15 matches
Mail list logo
