* add button group for multiple preview urls
* generate default + sub buttons for urls
* allow button group to render label without a localisation key
* remove the existing preview button
* add data-element attr for buttons for tours + tests
* use info button style
* set the target of the new window
* get the additional preview urls from the active variant
* Revert "Make sure the property editor layout is contained within its container (prevent Z-index bleed-through) (#13583)"
This reverts commit 8463d906a7.
* remove seemingly unused attribute readonly
* contain everything with contain:layout
this is set if the property editor is in preview mode to make sure all overlays work
* Revert "remove seemingly unused attribute readonly"
This reverts commit 7a2743e8f664e707e8df5022fe754dfd77c508ea.
* Revert "Make sure the property editor layout is contained within its container (prevent Z-index bleed-through) (#13583)"
This reverts commit 8463d906a7.
* remove seemingly unused attribute readonly
* contain everything with contain:layout
this is set if the property editor is in preview mode to make sure all overlays work
* Revert "remove seemingly unused attribute readonly"
This reverts commit 7a2743e8f664e707e8df5022fe754dfd77c508ea.
* Revert "Make sure the property editor layout is contained within its container (prevent Z-index bleed-through) (#13583)"
This reverts commit 8463d906a7.
* remove seemingly unused attribute readonly
* contain everything with contain:layout
this is set if the property editor is in preview mode to make sure all overlays work
* Revert "remove seemingly unused attribute readonly"
This reverts commit 7a2743e8f664e707e8df5022fe754dfd77c508ea.
* Added a longer timeout for the tests. Also bumped the timeout for isSuccessNotificationVisible
* Added a longer timeout for our tests and the isSuccessNotificationVisible method
* Updated the locator for the flaky test. The locator we had before could sometimes find two elements, which resulted in flaky tests.
* Bumped version of playwright
* Updated to use isSuccessNotificationVisible()
* Added a wait for timeout
* Updated to use isSuccessNotificationVisible()
* Bumped the timeouts
* Bumped our timeouts
* Bumped version of our testhelpers
* Updated the button for save and publish and added an wait for timeout
* Added a missing save for the test
* The test could sometimes find two locators. It should be fixes now
* Removed old usage of notification to be visible
* Removed unnecessary timeouts since we have defined the timeouts in the test helpers
* Add configuration/code to not run certain tests based on variables/release builds
* Applied longrunning testAttribute to the worst offenders (>200ms on my machine)
* Fix yaml notation
* split up windows/non windows test runs
* Added supression for moved tests
* Fix yaml validation issues
* Change yaml string parameter null value to empty string
* Convert empty strings to whitespace strings
* Rename and cleanup some paramater to better reflect why we use them
* Nightly build test
* Change nightly build authentication type
* template paramater fix
* Update nightly pipeline name
---------
Co-authored-by: Sven Geusens <sge@umbraco.dk>
* Add visuallyHiddenTexts area and keys to swedish
Translations contributed by @plannero
* Add missing localizations.
* Revert prettier formatting
* Format in visual studio
* Change default UpgradeUnattended value to true (#13281)
* add labels to default en.xml + small glitch fix
* Added test for checking if a settings model contains default value.
Fixed tests
* Bumped version
* Moved createSliderWithDefaultValue function to our testHelpers. Removed the use of count in test since there was only one
Sometimes a tab, e.g. a "block list settings model" might register some default values, but if the user never clicks on the tab then they are not registered due to how AngularJS renders views with "ng-if".
* Added test for checking if a settings model contains default value.
Fixed tests
* Bumped version
* Moved createSliderWithDefaultValue function to our testHelpers. Removed the use of count in test since there was only one
Sometimes a tab, e.g. a "block list settings model" might register some default values, but if the user never clicks on the tab then they are not registered due to how AngularJS renders views with "ng-if".
