Comments (10)
@DanielRyanSmith or @past, any insight into what might be getting in the way here?
from chromium-dashboard.
I'll look into this and report back ASAP. Thanks for bringing this up. 🙂
from chromium-dashboard.
As for the "Chromium Trial Name" field, the value that needs to be provided is from the origin_trial_feature_name
property, which is "MediaPreviewsOptOutPersistent" in this case.
@mfoltzgoogle Is this a deprecation trial? If so, then we have a bug in the form that needs to be fixed, as it should not require a usecounter value for deprecation trials. In this scenario, I would advise the workaround of providing an existing usecounter with a numeric value (e.g. "kOBSOLETE_PageDestruction"), and we will handle your request disregarding that value.
However, if this is not a deprecation trial, we have a separate problem in which we have no way to track usage of the feature. @past might have further opinions on moving forward if that is the case.
from chromium-dashboard.
Thank you for the prompt response, those workarounds allowed the form to be submitted 😁
As for the "Chromium Trial Name" field, the value that needs to be provided is from the origin_trial_feature_name
I was using the value from the name
field instead; maybe the form could be specific to refer to the origin_trial_feature_name
field to avoid future confusion
@mfoltzgoogle Is this a deprecation trial?
Yes, I set this up as a deprecation trial, because it's allowing sites to opt into existing behavior. Once I checked the "deprecation trial" checkbox it allowed me to submit the form with the dummy usecounter.
I'ts a good point that there is not a way to track usage of this trial yet. I can add a custom UMA for that.
from chromium-dashboard.
We can see your creation request submission on our side, so the problem has been mitigated. 🙂
Our validation checks on values in Chromium files is a recently-added feature, so your feedback in this situation has been valuable. We'll take steps to make this less confusing in the future.
from chromium-dashboard.
Sorry for these bumps as we improve these checks Mark and thanks for your patience, much appreciated!
Note that the Intent to Experiment field should also be mandatory (we'll fix that), so you need to request approval from API Owners before we can proceed with the trial.
from chromium-dashboard.
The intent to experiement was LGTMed.
https://groups.google.com/a/chromium.org/g/blink-dev/c/f_x-iPGZSPg/m/QB6nATbuBAAJ
from chromium-dashboard.
Let me know if there are other steps required.
from chromium-dashboard.
Thanks for that pointer, I'll follow up in the OT ticket. Let's use this issue for tracking the Chromestatus bug fixing work.
from chromium-dashboard.
Deprecation trials are no longer required to provide a usecounter value in the OT creation request form.
from chromium-dashboard.
Related Issues (20)
- Features should not show up on the roadmap as shipping purely based on browser version number in prepare to ship HOT 2
- "OT Contacts" argument needs to be added to OT creation Chromestatus request HOT 1
- A new enum field should be added to Stage to represent the creation status of the origin trial HOT 1
- OT Creation/Activation endpoints need to be started and tested
- Activity log entries miss important information
- OT creation does not work as intended, pre Chromestatus-OT automation HOT 4
- Feature with 3 OT stages has 2 of them pointing to the same trial ID HOT 4
- Trial name should be limited to 63 characters in trial creation HOT 2
- Make the advice to write unit tests for OT more prominent
- Duplicate and missing web features
- Report on the state of feature verification
- The OT creation form should accept WebDX Feature counters too
- OT extension request data moved to old blank extension stage
- Outbound emails failures when to=[] HOT 1
- Use another project name for the local datastore emulator
- Don't require other gate approval prior to API owners
- Restore comments on ChromedashToast.showMessage
- Mta-sts.croydon.gov.uk HOT 3
- Add functionality to have Playwright tests mimic admin actions
- Email input field in production environment does not suggest previously entered emails
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from chromium-dashboard.