* adds global, workpad css styling feature
* fixes checkered position and default CSS in textarea
* adds global, workpad css styling feature
* fixes checkered position and default CSS in textarea
* Added global styles to page manager
* Added 'apply stylesheet' button
* fix after rebase
* change style to css
* move default workpad CSS class to constant
* unwind the empty page color pieces
This changes the header to be conditionally rendered based on the k7design UI setting. If the setting is false, the header is rendered as before. If it is true, the header is hidden and the breadcrumbs are set via the Kibana breadcrumbs api.
Url's from EMS ((files and tiles) should be resolved ad-hoc. The one that is stored in the saved object should not be used. This change removes the URL from the saved object. It also provides fallback functionality so old saved objects continue to be loaded correctly.
* Specifying the timeout for the msearch in the body
* Revert "Specifying the timeout for the msearch in the body"
This reverts commit 7b07bfa2e6.
* Fixing the courier and the index pattern execute script timeouts
* [pageObjects/common] remove unused runScript method
* [pageObjects/common] remove almost unused doesCssSelectorExist method
* [pageObjects/graph] convert to use find/testSubjects services
* [pageObjects/discover] refactor out remote service
* [pageObjects/pointSeries] refactor out remote service
* [pageObjects/monitoring] refactor out remote service
* [ftr] refactor uses of remote to use browser or find
* [ftr/services/remote] wrap remote with browser service
* [pageObjects/security] refactor out uses of remote
* [ftr/services/browser] isolate element calls to find
* [ftr] rename remote service to __leadfoot__
* [ftr/leadfoot] cleanup some renames in find, keep names in other tests
- Fixes 25707 by parsing the colors generated for the node and adding a
try/catch to prevent an errors by returning the default color
- Set the min bounds to zero when there is only one data point
Provides protection against reading/re-indexing against an index with missing
shards which could result in data loss. This shouldn't be common, as the Saved
Object indices should only ever have a single shard. This is more to handle
instances where customers manually expand the shards of an index.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>