type ModelContextToolIssueDetails extends objectPhilip Pfaffeshould we use GenericIssueDetails instead? cc @pfa...@chromium.org
Anders Hartvoll RuudI think this could be a GenericIssue, yes. It can already link to nodes and also attributes.
Anders Hartvoll RuudOK, that works for me; I'll take this back to WIP while getting that sorted.
OK, done.
// A collection of optional fields that may store additional data depending
// on the issue code.Anders Hartvoll Ruudnit-to-self: Oops, this comment should stay above `InspectorIssueDetails` ...
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
window.navigator.modelContextTesting.listTools();Is this required?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
window.navigator.modelContextTesting.listTools();Is this required?
Currently, yes. Schemas of form-backed tools are computed on demand. It's not (directly) triggered by loading, or other document lifecycle stages.
Depending on this API is not _ideal_, however. I guess we'll soon be adding some devtools protocol support for listing tools. Should we land that first, and use that instead?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
window.navigator.modelContextTesting.listTools();Anders Hartvoll RuudIs this required?
Currently, yes. Schemas of form-backed tools are computed on demand. It's not (directly) triggered by loading, or other document lifecycle stages.
Depending on this API is not _ideal_, however. I guess we'll soon be adding some devtools protocol support for listing tools. Should we land that first, and use that instead?
Thanks for clarifying, I'm fine landing with the API for now. We'll notice if it gets removed or changes signifantly :)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
window.navigator.modelContextTesting.listTools();Anders Hartvoll RuudIs this required?
Philip PfaffeCurrently, yes. Schemas of form-backed tools are computed on demand. It's not (directly) triggered by loading, or other document lifecycle stages.
Depending on this API is not _ideal_, however. I guess we'll soon be adding some devtools protocol support for listing tools. Should we land that first, and use that instead?
Thanks for clarifying, I'm fine landing with the API for now. We'll notice if it gets removed or changes signifantly :)
Acknowledged
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
From googleclient/chrome/chromium_gwsq/ipc/config.gwsq:
IPC: cl...@chromium.org
📎 It looks like you’re making a possibly security-sensitive change! 📎 IPC security review isn’t a rubberstamp, so your friendly security reviewer will need a fair amount of context to review your CL effectively. Please review your CL description and code comments to make sure they provide context for someone unfamiliar with your project/area. Pay special attention to where data comes from and which processes it flows between (and their privilege levels). Feel free to point your security reviewer at design docs, bugs, or other links if you can’t reasonably make a self-contained CL description. (Also see https://cbea.ms/git-commit/).
IPC reviewer(s): cl...@chromium.org
Reviewer source(s):
cl...@chromium.org is from context(googleclient/chrome/chromium_gwsq/ipc/config.gwsq)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |