-
Notifications
You must be signed in to change notification settings - Fork 172
Create unified nav elements for Perf APIs. #229
Conversation
Hi Joe, I'm a bit confused here. Why have you added an entry to GroupData for this API, but also made a separate PerformanceSidebar Macro? The added GroupData is read and turned into a sidebar by the APIRef macro: https://github.com/mozilla/kumascript/blob/master/macros/APIRef.ejs See https://developer.mozilla.org/en-US/docs/Web/API/WebVR_API for an example of how this is used. I'll review your GroupData entry too. |
macros/GroupData.json
Outdated
"PerformanceNavigationTiming", | ||
"PerformanceObserver", | ||
"PerformanceResourceTiming", | ||
"window.performance" ], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Window.performance
macros/GroupData.json
Outdated
"PerformanceNavigationTiming.redirectCount", | ||
"PerformanceNavigationTiming.type", | ||
"PerformanceNavigationTiming.unloadEventEnd", | ||
"PerformanceNavigationTiming.unloadEVentStart", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unloadEventStart
@chrisdavidmills PTAL |
@chrisdavidmills Is there anything else I need to do to this? |
Sorry Joe; I've still not had a chance to go through this. I'll get to it soon, promise. |
Do you know what? I'm drowning in work, and having a terrible time finding the time to look at this. Sorry Joe. @Elchi3 , this looks OK to me from a cursory glance. Can you give it a second look if you get the chance? |
Thanks, guys!
Joe Medley | Technical Writer, Chrome DevRel | jmedley@google.com |
816-678-7195
*If an API's not documented it doesn't exist.*
…On Tue, Jul 25, 2017 at 7:26 AM, Chris Mills ***@***.***> wrote:
Do you know what? I'm drowning in work, and having a terrible time finding
the time to look at this. Sorry Joe.
@Elchi3 <https://github.com/elchi3> , this looks OK to me from a cursory
glance. Can you give it a second look if you get the chance?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#229 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AH0vi3YQkJF81s09SQtS3V_iUMJP55W7ks5sRfsZgaJpZM4OF6_q>
.
|
This question still stands. What's the motivation for {{PerformanceSidebar}} ?
|
Sorry for the turmoil. What I had in mind is slowly coming back to me. I
had intended to add more to what the macro showed after getting it sanity
checked.To be honest, I'm now thinking my reasoning was a bit shaky. Here's
the problem I thought I was solving.
The APIs listed in group data are all related yet many of them have
separate entries in groupdata, and separate overview pages. At the time I
opened this PR, I believed I was saving us the trouble of editing a few
hundred APIRef() macro calls (shaky reasoning).
Unless someone has another idea, let me take another shot at this using
just groupdata. Again, sorry for the turmoil.
Joe
Joe Medley | Technical Writer, Chrome DevRel | jmedley@google.com |
816-678-7195
*If an API's not documented it doesn't exist.*
…On Tue, Jul 25, 2017 at 7:43 AM, Florian Scholz ***@***.***> wrote:
This question still stands. What's the motivation for
{{PerformanceSidebar}} ?
Why have you added an entry to GroupData for this API, but also made a
separate PerformanceSidebar Macro?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#229 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AH0vi2M3UnI6rrwHGFagjXGccB7--Vutks5sRf8ngaJpZM4OF6_q>
.
|
No worries, Joe. I think this should be good with just the GroupData entries. (Refactoring the sidebars to be somewhat more coherent and solid is on my radar, but won't happen anytime soon. Also, we need to first find out how much they are used to judge if it is worth our time to improve this code). |
I actually thought unifying the sidebar and creating a master overview page
would be a lot of bang for very few bucks. I personally think the ability
to test performance in the wild has enormous value.
Joe Medley | Technical Writer, Chrome DevRel | jmedley@google.com |
816-678-7195
*If an API's not documented it doesn't exist.*
…On Tue, Jul 25, 2017 at 11:51 AM, Florian Scholz ***@***.***> wrote:
No worries, Joe. I think this should be good with just the GroupData
entries.
(Refactoring the sidebars to be somewhat more coherent and solid is on my
radar, but won't happen anytime soon. Also, we need to first find out how
much they are used to judge if it is worth our time to improve this code).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#229 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AH0vi9vbo3U84BhDtvcWl_4eVZJknGUvks5sRjlLgaJpZM4OF6_q>
.
|
Performance navigation, take II. This is part 1 of 3. 1. Create "Performance API" in GroupData.json. |
macros/GroupData.json
Outdated
"title": "Long Tasks API" }, | ||
{ "url": "/en-US/docs/Web/API/Navigation_timing_API", | ||
"title": "Navigation Timing API" }, | ||
{ "url": "/en-US/docs/Web/API/Navigation_timing_API/Using_Navigation_Timing", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://developer.mozilla.org//en-US/docs/Web/API/Navigation_timing_API/Using_Navigation_Timing
This page page looks useless. Are you planning to write something here? If not, I think it shouldn't be here for now.
macros/GroupData.json
Outdated
"TaskAttributionTiming.containerName", | ||
"TaskAttributionTiming.containerSrc", | ||
"TaskAttributionTiming.containerType" ], | ||
"events": [ "Performance.onresourcetimingbufferfull" ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs to be the name of the event "resourcetimingbufferfull" to create a link to the event page:
https://developer.mozilla.org/en-US/docs/Web/Events/resourcetimingbufferfull
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See the two comments, but we are really close!
Also, note that guides are only used by {{DefaultAPISidebar("Performance API")}}, so we've been using that on overview pages (c.f. https://developer.mozilla.org/en-US/docs/Web/API/Gamepad_API) and {{APIRef("Performance API")}} on reference pages (c.f. https://developer.mozilla.org/en-US/docs/Web/API/Gamepad). (Probably not ideal, but this is how this stuff currently works, ICYDK.)
PTAL |
Almost! I meant This is used to build https://developer.mozilla.org/en-US/docs/Web/Events/ |
PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great!
- mdn/kumascript#229 - GroupData: Performance API - mdn/kumascript#241 - DekiScript-Page, DekiScript-Wiki: API calls - mdn/kumascript#246 - AddonSidebar: Fixes, Working with files - mdn/kumascript#247 - AddonSidebar: Publist and Distribution - mdn/kumascript#252 - GroupData: Media Streams API - mdn/kumascript#254 - GameTechBox: Add pt-BR - mdn/kumascript#258 - L10nStatusOverview: Add pr-BR - mdn/kumascript#259 - AddonSidebar: Themes - mdn/kumascript#260 - AddonSidebar: Contact method - mdn/kumascript#261 - many macros: Use mdn.localStringMap - mdn/kumascript#262 - GroupData: Stream API methods -> properties
- mdn/kumascript#229 - GroupData: Performance API - mdn/kumascript#241 - DekiScript-Page, DekiScript-Wiki: API calls - mdn/kumascript#246 - AddonSidebar: Fixes, Working with files - mdn/kumascript#247 - AddonSidebar: Publist and Distribution - mdn/kumascript#252 - GroupData: Media Streams API - mdn/kumascript#254 - GameTechBox: Add pt-BR - mdn/kumascript#258 - L10nStatusOverview: Add pr-BR - mdn/kumascript#259 - AddonSidebar: Themes - mdn/kumascript#260 - AddonSidebar: Contact method - mdn/kumascript#261 - many macros: Use mdn.localStringMap - mdn/kumascript#262 - GroupData: Stream API methods -> properties
No description provided.