On Sat, 29 Oct 2011 04:18:37 +0200, Chris Pearce cpea...@mozilla.com
wrote:
Should we still dispatch the fullscreenchange event to the element which
requested fullscreen if the element was removed from its document before
the event was dispatched? What if the element was added to another
On Wed, Oct 19, 2011 at 11:57 PM, James Graham jgra...@opera.com wrote:
On 10/19/2011 06:40 AM, Anne van Kesteren wrote:
Is that an acceptable limitation? Alternatively we could postpone the
nested fullscreen scenario for now (i.e. make requestFullscreen fail if
already fullscreen).
I
27.10.2011 3:11, Ashley Sheridan wrote:
Try telling me
Google isn't aware of HTML5 in web pages and I'll laugh.
OK, I'll try: Google does not care about new HTML5 elements. Do you feel
amused now?
Can you please now do me, and others, a favor and give some evidence of
actual Google
On Sat, 2011-10-29 at 16:38 +0300, Jukka K. Korpela wrote:
Can you please now do me, and others, a favor and give some evidence of
actual Google behavior in this respect? If it's something that we need
to be aware of, it should be observable from outside Google, i.e. when
using Google,
On Sat, Oct 29, 2011 at 3:38 PM, Jukka K. Korpela jkorp...@cs.tut.fiwrote:
It is certainly wise to keep table as dual (tabular data vs. layout) for
compatibility, instead of introducing new elements to distinguish them - no
matter how logical or semantic such an idea might sound.
I heard
