5 results found

1. CSS code validation

   As a frequent user of the code editor and a builder that surrounds each of the variants I build with their own unique DOM ID so that I can prefix each CSS rule with same ID and eliminate any possibility of style bleed into other areas of the page

   I would like to see some of the current CSS validation remarks related to ID use removed. the list includes the following but their may be more:
   1. 'don't use ids as selectors' (as it is 100% valid CSS and actually faster in the rendering engine)
   2. 'really, 2 ids?' - yes. it is actually common for me. I always surround my variant with its own unique id and there may be downstream ids that I need to modify. pretty common actually.

   So that I can have a warning list that is accurate and useful.

   The current model results in a warning list that is actually unusable for me because every single line shows up with a warning because I use IDs in every single rule. I understand the models that recommend only classnames to be used, I just don't adhere to them, I write object-oriented CSS for speed and efficiency. IDs in CSS and the DOM are a valid and effective construct if used properly. Given the number of models out there, it is probably best to only warn when rules have actual potential issues.

   As a frequent user of the code editor and a builder that surrounds each of the variants I build with their own unique DOM ID so that I can prefix each CSS rule with same ID and eliminate any possibility of style bleed into other areas of the page

   I would like to see some of the current CSS validation remarks related to ID use removed. the list includes the following but their may be more:
   1. 'don't use ids as selectors' (as it is 100% valid CSS and actually faster in the rendering engine)
   2. 'really, 2 ids?' -… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Future Consideration  ·  AdminDejan Dragusin (Senior Product Manager, Optimizely) responded

   This is something that hasn't been reviewed in some time.

   We plan to rework how developers work with WEB later this year. We will take this into account.

2. Improved clarity around scheduled experiments

   As an experimentation user, I want the UI around scheduled experiments to more clear about the experiment status.

   Currently, the experiment status is either "Not Started" or "Paused". It would be great if the experiment status instead was simply "Scheduled", or alternatively "Paused (Scheduled)" / "Not Started (Scheduled)".

   Additionally, when changing a paused scheduled experiment, there is a warning "Publish your experiment if you want your draft changes to go live on the scheduled date.". However, when clicking Publish, the preferred option "Publish Only" is not highlighted and instead "Publish and Start" is highlighted. This might cause someone to accidentally start the experiment.
   Since the "Publish Only" is the option a customer is most likely to need, I would suggest highlighting that one instead.

   As an experimentation user, I want the UI around scheduled experiments to more clear about the experiment status.

   Currently, the experiment status is either "Not Started" or "Paused". It would be great if the experiment status instead was simply "Scheduled", or alternatively "Paused (Scheduled)" / "Not Started (Scheduled)".

   Additionally, when changing a paused scheduled experiment, there is a warning "Publish your experiment if you want your draft changes to go live on the scheduled date.". However, when clicking Publish, the preferred option "Publish Only" is not highlighted and instead "Publish and Start" is highlighted. This might cause someone to accidentally… more

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Ability to track MAU consumption per project when using Custom Snippets

   Currently in admin centre the reporting available for MAU's per project does not provide data if the customers projects were set up using custom snippets. As custom snippets are a popular way to set this up, it would be great to be able to able to report on this.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  0 comments  ·  Reporting  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Include ability to target html elements based on their css specificity.

   Currentlh when using the Visual editor and an element is selected such as an H1, the css class or ID attributes are not accounted for in the editor.

   Sometime is is necessary to be more specific, such as

   H1 vs H1.classname

   The idea is to include an option to use specificity and have the editor use the ID or classname based on a setting.

   Such as...

   Use HTML element only (H2)
   Use HTML ID (#id-name)
   Use HTML element + CSS Class name (H2.classname)

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Do not remove code when changing activation targets.

   Frequently I need to switch my coding / set up from a staging to a production environment. Optimizely warns me and then REMOVES all my code.

   This is fine if you are a basic non-technical user.

   It would be better if this was an optional change.

   Possibly provide a check box and a message in the button (see screenshot) - which would allow me to change the targeting.

   •  

   •  

   7 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating