On Mon, Nov 4, 2013 at 5:07 PM, Elliott Sprehn <[email protected]> wrote:
> On Mon, Nov 4, 2013 at 4:55 PM, Ryosuke Niwa <[email protected]> wrote: > >> On Mon, Nov 4, 2013 at 3:12 PM, Elliott Sprehn <[email protected]>wrote: >> >>> On Mon, Nov 4, 2013 at 2:19 PM, Ryosuke Niwa <[email protected]> wrote: >>> >>>> 99 is a very high upper bound while it would still allow us to >>>> implement the optimization we're thinking of. >>>> >>>> I'm of the opinion that we should use exactly one attribute for this >>>> feature. >>>> >>> >>> Can you explain what this optimization is? It's difficult to figure out >>> how to address your issues without knowing what optimization it prevents. >>> >> >> I'm not sure if I wasn't clear here but I'm saying that having an upper >> bound of 9 or 99 would address the concern of not being able to implement >> the particular optimization we're considering. >> > > Yeah; what optimization do you plan to implement though? > There are many optimizations you can implement if the number of parsed attributes is bounded at compilation time, and that's all I can say. But the bigger issue is that src-N resembles no other content attribute we have as others pointed out on this thread. While the picture element proposal had issues of having to deal with source elements being added or removed dynamically, at least authors are familiar with the pattern. src-N is worse in that it's both complicated and foreign to authors as well as existing tools as Mike pointed out. - R. Niwa
_______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
