Re: [whatwg] [2D Canvas] Proposal: batch variants of drawImage

2014-08-05 Thread Brian Blakely
On Tue, Aug 5, 2014 at 11:21 AM, Justin Novosad wrote: > On Tue, Aug 5, 2014 at 7:47 AM, Ashley Gullen wrote: > > > I am against this suggestion. If you are serious about performance then > > you should use WebGL and implement your own batching system, which is > what > > every major 2D HTML5 ga

[whatwg] Better DOM hooks for polyfilling CSS properties?

2014-07-10 Thread Brian Blakely
Problem === It's difficult to know when an unsupported property was set for any arbitrary element, and manually sifting through stylesheets isn't very easy. This makes polyfilling CSS harder than it needs to be. Strawman === The endgoal is to easily get a NodeList containing elements that have

Re: [whatwg] Canvas-Only Document Type

2014-07-09 Thread Brian Blakely
Thank you for those informative comments, Elliott. My own tests in Firefox reflect yours and Boris's feedback. While there is clearly overhead from non-Canvas vectors, it's pretty minor. On Wed, Jul 9, 2014 at 12:43 PM, Elliott Sprehn wrote: > > On Tue, Jul 8, 2014 at 7:37 A

Re: [whatwg] Canvas-Only Document Type

2014-07-08 Thread Brian Blakely
I agree, that would be valuable. This proposal is coming from the direction that sweeping out the main thread, and leaving only what is necessary for a full Canvas experience, would benefit such experiences. On Mon, Jul 7, 2014 at 11:14 PM, Robert O'Callahan wrote: > If you want jank-free canvas

Re: [whatwg] Canvas-Only Document Type

2014-07-08 Thread Brian Blakely
Thank you for this information, Boris. Did you collect this with Firefox's own devtools? I'd like to set up a full-view Canvas document and see how it profiles. FWIW, memory is one of several optimizations one could conjure, and it is the culmination of these that (in concept) creates a more pol

Re: [whatwg] Canvas-Only Document Type

2014-07-08 Thread Brian Blakely
gt;>>>> buttons and so on, which are positioned over the canvas. In particular >>>>> text inputs are useful for things like name entry or logins even for >>>>> games, and are typically difficult and error-prone to reimplement in only >>>>>

Re: [whatwg] Canvas-Only Document Type

2014-07-08 Thread Brian Blakely
Keep in mind my suggestion doesn't take away something that once solved your use case, or even adequately upheld the philosophy of an accessible Web. It simply doesn't try to solve it, which is a different thing. On Mon, Jul 7, 2014 at 7:53 PM, Nils Dagsson Moskopp wrote: > "Brian M. Blakely" w

[whatwg] Canvas-Only Document Type

2014-07-07 Thread Brian Blakely
Floating a concept for a document mode which eschews CSS and the DOM to enable a more jank-free Canvas surface. Depending on how this allows for optimization, might be used well for games, VR, wearables, and ultra-portable or high-performance apps. Probably most beneficial to memory usage and firs

Re: [whatwg] Comments on

2014-02-03 Thread Brian Blakely
On Fri, Jan 31, 2014 at 7:31 PM, Ian Hickson wrote: > On Wed, 18 Dec 2013, Brian Blakely wrote: > > On Wed, Dec 18, 2013 at 2:13 PM, Ian Hickson wrote: > > > On Wed, 18 Dec 2013, Brian Blakely wrote: > > > > On Tue, Dec 17, 2013 at 3:14 PM, Ian Hickson wrote: &g

Re: [whatwg] Comments on

2013-12-18 Thread Brian Blakely
On Wed, Dec 18, 2013 at 2:13 PM, Ian Hickson wrote: > On Wed, 18 Dec 2013, Brian Blakely wrote: > > On Tue, Dec 17, 2013 at 3:14 PM, Ian Hickson wrote: > > > > > > I've added a rule to the spec that says that viewports have to be > > > pannable so you

Re: [whatwg] Add "Switch" Type

2013-12-18 Thread Brian Blakely
On Tue, Nov 19, 2013 at 6:29 AM, Elliott Sprehn wrote: > On Tue, Nov 19, 2013 at 1:37 AM, Jonas Sicking wrote: > > > Realistically speaking, I don't think this will help much at all. Few > > websites like using the default styling for form controls anyway and > > so people would be just as unhapp

Re: [whatwg] Comments on

2013-12-18 Thread Brian Blakely
On Tue, Dec 17, 2013 at 3:14 PM, Ian Hickson wrote: > I've added a rule to the spec that says that viewports have to be pannable > so you can see all of a dialog, but I don't know how feasible that really > is. > I could see implementations using shadow s to satisfy this It might be beneficial

Re: [whatwg] Concerns with

2013-11-02 Thread Brian Blakely
On Sat, Nov 2, 2013 at 5:29 PM, Ian Hickson wrote: > On Sat, 2 Nov 2013, Brian Blakely wrote: > > > > 1. When a modal dialog is active, the user can still scroll the > > underlying page. > > Why is that a bug? > By its nature, a modal view blocks interaction with

Re: [whatwg] Comments on

2013-11-02 Thread Brian Blakely
> > > 4. Why isn't the dialog horizontally centered in the viewport? The spec > > just mentions vertical centering and 'top'. > > The horizontal centering is done via the default CSS. The vertical > centering can't be done with CSS, hence all the prose about it. That isn't true anymore. There

[whatwg] Concerns with

2013-11-02 Thread Brian Blakely
Using Chrome Canary and http://demo.agektmr.com/dialog/ as a reference implementation. Are these spec concerns or Chromium implementation concerns? Not completely clear on this. 1. When a modal dialog is active, the user can still scroll the underlying page. 2. Even if the root element

[whatwg] Add "Switch" Type

2013-09-20 Thread Brian Blakely
"iPhone OS" introduced the switch control (http://i.imgur.com/TA79fo2.png) in 2007. Since then, there have been many attempts to recreate this on the Web Platform by hacking existing control types and using a lot of meaningless markup, to varying degrees of success. The proposal is to add a "swit

Re: [whatwg] Canonical Image and Color

2013-08-28 Thread Brian Blakely
On Fri, Jul 12, 2013 at 1:32 PM, Ian Hickson wrote: > You are welcome to register these on the wiki and convince people to use > them, sure. Seems like they already have solutions, though, as you show: Would you kindly link me to the wiki? > Sounds like this is already solved, then. > In a s

Re: [whatwg] Canonical Image and Color

2013-02-11 Thread Brian Blakely
UI, respectively. On Mon, Feb 11, 2013 at 5:41 PM, Tab Atkins Jr. wrote: > On Mon, Feb 11, 2013 at 2:33 PM, Brian Blakely > wrote: > > * Proposal > > > > Meta elements for defining a canonical image and color to be associated > > with the page(s) in which they ar

[whatwg] Canonical Image and Color

2013-02-11 Thread Brian Blakely
* Proposal Meta elements for defining a canonical image and color to be associated with the page(s) in which they are included. This is intended for use by user agents and third-party applications (such as social networks), referred to collectively as "parsers" in this document. It is inspired b

Re: [whatwg] Proposal: "Offline-Capable" Meta Tag and API Indicates Application's Ability to Function Without Network Connection

2012-06-07 Thread Brian Blakely
-only, forever" and a simple API for a dev will encourage implementation. Cheers, -Brian On Wed, Jun 6, 2012 at 7:49 PM, Ian Hickson wrote: > On Fri, 27 Jan 2012, Brian Blakely wrote: > > On Fri, Jan 27, 2012 at 4:50 PM, Ian Hickson wrote: > > > On Fri, 27 J

Re: [whatwg] Proposal: "Offline-Capable" Meta Tag and API Indicates Application's Ability to Function Without Network Connection

2012-01-27 Thread Brian Blakely
ble a native-like app download process that is, again, always the same on the same UA, instead of varying from application to application. -Brian On Fri, Jan 27, 2012 at 4:50 PM, Ian Hickson wrote: > On Fri, 27 Jan 2012, Brian Blakely wrote: > > > > Hey Ian, > > > > "

Re: [whatwg] Proposal: "Offline-Capable" Meta Tag and API Indicates Application's Ability to Function Without Network Connection

2012-01-27 Thread Brian Blakely
ose portions of the app that they would like to cache long-term, but suppose the user needs the entire thing? In that case, 700MB could likely lowballing by quite a bit. On Fri, Jan 27, 2012 at 1:34 PM, Ian Hickson wrote: > On Wed, 12 Oct 2011, Brian Blakely wrote: > > > > Trigger

Re: [whatwg] Proposal: "Offline-Capable" Meta Tag and API Indicates Application's Ability to Function Without Network Connection

2011-10-21 Thread Brian Blakely
*Background Downloading* *Problem* * * Data transfer ends when the user closes the browser, making huge 700MB applications impossible. How many are willing to keep a loading tab open for half an hour or more? The current paradigm of page loading does not work for very large applications that nee

Re: [whatwg] Proposal: "Offline-Capable" Meta Tag and API Indicates Application's Ability to Function Without Network Connection

2011-10-13 Thread Brian Blakely
ing app data > synchronization. The motivation being that there should be a > universal way to manage the > state of all offline capable apps at the browser/OS level. > > On Wed, Oct 12, 2011 at 6:06 PM, Brian Blakely > wrote: > > *The element:* > > > > &g

[whatwg] Proposal: "Offline-Capable" Meta Tag and API Indicates Application's Ability to Function Without Network Connection

2011-10-12 Thread Brian Blakely
*The element:* *Its purpose:* Trigger a UA-native indication to the user that the current application's primary and entire collection of features can be used without a network connection. *API:* A simple API in the form of a document.offlineCapable boolean setter/getter would allow an applicatio

Re: [whatwg] : A 3D Equivalent to

2009-12-09 Thread Brian Blakely
:25 PM, Ian Hickson wrote: > On Fri, 30 Oct 2009, Brian Blakely wrote: > > > > To ensure HTML remains semantic as the web makes its gradual transition > > to 3D rich interfaces and content, I am submitting a proposal for > > WHATWG's consideration. > > I e

[whatwg] Hand the function of over to ?

2009-11-05 Thread Brian Blakely
I can only imagine the usage of will be utilized more productively if its intuitive purpose (arbitrary contact/postal addresses) were its actual function. As our friends at HTML5 Doctor illustrate, it is all too easy to jump to conclusions and use this element incorrectly. Perhaps a element wou

Re: [whatwg] : A 3D Equivalent to

2009-11-03 Thread Brian Blakely
eaking totally of-the-cuff for the sake of clarity: <face id="content-face" etc etc /> ..and in CSS: map-model: url(cube.xml) content-face stretch etc etc; -Brian Simon Fraser wrote: On Nov 2, 2009, at 4:26 PM, Brian Blakely wrote: > * Though it does not have properti

Re: [whatwg] : A 3D Equivalent to

2009-11-02 Thread Brian Blakely
CYp, We are speaking about a native, semantic 3D media type. It is inherently compatible with 3D CSS and requires no additional code to display. This is very different from a 2D rendering based on 3D properties (as with VRML and ). -Brian 2009/11/2 CYp : > * 2D bitmaps are only partially comp

Re: [whatwg] : A 3D Equivalent to

2009-11-02 Thread Brian Blakely
Spinning Cube Example Integrating 3D Media Type with Current Techniques --- (note: the only significant difference between this and currently implemented technology is the media type and additional CSS properties suited specifical

Re: [whatwg] : A 3D Equivalent to

2009-11-02 Thread Brian Blakely
Simon, * Though it does not have properties for clipping, Webkit's proposed implementation of 3D CSS does have them for perspective. Clipping, lighting, texture stretching and additional considerations could also be a part of that spec, but those are discussions for the CSS WG. Without a 3D medi

Re: [whatwg] : A 3D Equivalent to

2009-11-02 Thread Brian Blakely
Additional clarification on this proposal: A "model" Element Never Becomes a Wafer --- Right now, if you try to act on conventional HTML elements with 3D CSS, those elements become wafers. See here: http://webkit.org/blog/386/3d-transforms/

Re: [whatwg] : A 3D Equivalent to

2009-11-02 Thread Brian Blakely
language for the web isn't a good idea. I > think the idea has some huge potential. I just don't think that layering it > on top of HTML with all of it's legacy concerns and also it's document > centric model is a good idea for the above practical concerns. > > Dav

Re: [whatwg] : A 3D Equivalent to

2009-11-02 Thread Brian Blakely
David, Excellent perspectives, and there are certainly format decisions that have to be made as a matter of course, just as there have been for . I do not agree with two of your points: * A static 3D rendering is equal to a 2D bitmap * JavaScript is necessary to display 3D content My brief coun

Re: [whatwg] : A 3D Equivalent to

2009-11-01 Thread Brian Blakely
er code required. This source could be in X3D format, or 3DS, MA, etc. Whichever the vendors eventually decide to support (hopefully the same format :) -Brian On Sun, Nov 1, 2009 at 8:31 PM, Simon Fraser wrote: > On Oct 30, 2009, at 6:09 PM, Brian Blakely wrote: > > To ensure HTM

Re: [whatwg] : A 3D Equivalent to

2009-11-01 Thread Brian Blakely
Bjartur, Great contribution, greatly appreciated. I am in partial agreement with you, and an XHTML2 approach was certainly something I pondered. A new tag, however, makes more sense in the HTML5 way of doing things, in which native media types are getting their own semantic tags: (sound), (ye

[whatwg] : A 3D Equivalent to

2009-10-30 Thread Brian Blakely
To ensure HTML remains semantic as the web makes its gradual transition to 3D rich interfaces and content, I am submitting a proposal for WHATWG's consideration. The below examples contain HTML as it exists now, the current working standard, and finally, a combination of both concepts. NOTES AND