- From: Ilya Grigorik <igrigorik@google.com>
- Date: Thu, 6 Nov 2014 11:56:16 -0800
- To: Ehsan Akhgari <ehsan.akhgari@gmail.com>
- Cc: Nic Jansma <nic@nicj.net>, Jonas Sicking <jonas@sicking.cc>, Eli Perelman <eperelman@mozilla.com>, Yoav Weiss <yoav@yoav.ws>, public-web-perf <public-web-perf@w3.org>
- Message-ID: <CADXXVKrp-cuBud8CFQegt2VdFvh-91b1DwQPfrcntHsxOiZyhw@mail.gmail.com>
On Fri, Oct 17, 2014 at 9:58 AM, Nic Jansma <nic@nicj.net> wrote: > I'm not sure if any of the browsers have built in special handling (for > dev tools, diagnostics, etc) of those marks. Vendors? > > We don't, we should. Opened a bug for Chrome CDT: crbug.com/431008 ig On Fri, Oct 17, 2014 at 11:05 AM, Ehsan Akhgari <ehsan.akhgari@gmail.com> wrote: > I grepped through the Blink and Chromium source code a while ago looking > for mentions of these names, and couldn't find any. > > On Fri, Oct 17, 2014 at 12:58 PM, Nic Jansma <nic@nicj.net> wrote: > >> I'm not sure if any of the browsers have built in special handling (for >> dev tools, diagnostics, etc) of those marks. Vendors? >> >> A casual web search shows numerous hits on blogs, etc where their use is >> being recommended. >> >> For future reference, would "namespacing" the marks, such as prefixing >> them with "standard:" have been the recommended approach? When designing >> UserTiming, we wanted to *suggest* standardized names that developers >> could use, if they were inclined. The spec is careful to not mention any >> expectation out of using these standard names. >> >> - Nichttp://nicj.net/ >> @NicJ >> >> On 10/13/2014 4:49 PM, Jonas Sicking wrote: >> >> On Mon, Oct 13, 2014 at 11:24 AM, Nic Jansma <nic@nicj.net> <nic@nicj.net> wrote: >> >> Hi Eli! >> >> In hindsight, I would agree with both of your recommendations. >> >> At this point though, with UserTiming being a W3C Recommendation, I think >> that changing the names would bring confusion. They're also only seen by >> developers. >> >> If there are any additional "standard" marks you can think of that would be >> useful, please let us know as well. >> >> Hi Nic, >> >> It somewhat concerns me that we say "use whatever name mark you want, >> it's just a string for you to give your own meaning to", but that we >> then turn around and say "except for these names, these have special >> behavior. Don't use these unless you mean exactly what we define them >> to mean". >> >> This is something that we've stayed away from with for example Element >> class names or id values. Various proposals have been made which gave >> special meanings to class names or id values, but they have always >> been shot down because things are just simpler if those are namespaces >> owned entirely by authors. >> >> Has any browsers actually implemented any browser features using the >> defined mark names? >> >> / Jonas >> >> >> >> > > > -- > Ehsan >
Received on Thursday, 6 November 2014 19:57:24 UTC