-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[K8] Added Inter
font files for new theme
#102359
Conversation
Updated the `Fonts` file to accept a `themeVersion` and only use the old Beta files if `v7`.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM when running locally, looks like the visual testing stuff needs updated screenshots, which I'd harvest from the GCS Uploads once the build is complete.
Thanks @spalger , that's the plan! 🤞 |
@@ -24,6 +24,7 @@ export interface RenderingMetadata { | |||
i18n: typeof i18n.translate; | |||
locale: string; | |||
darkMode: boolean; | |||
themeVersion?: string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why optional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mainly because there's an import of the Font file that doesn't have access to the current theme version.
<Fonts url={uiPublicURL} /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hum, yea. Ideally we'd want to adapt these two calls from security to retrieve the themeVersion setting, however it wouldn't do much, as these pages are rendered when security is enabled and user not authenticated, meaning that it would default to v8
anyway, so I guess having it optional and performing the default/fallback in core's component probably makes sense.
jenkins, test this (restarting due to jenkins upgrade) |
jenkins, test this I don't really understand why this one keeps timing out or how it would be related to this PR, so trying again for the night.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@spalger it should not need to add it, because it's waiting for scrollWidth > clientWidth [00:20:26] │ debg scrollWidth: 938, clientWidth: 938 ist should be fine when the agent file is being added, but it just continues? |
Ok, I think I know what could work, scrollWidth: 1020, clientWidth: 938 in the test are not converted to numbers
so it should be
Then the check should work, seems this PR changed the widths of the columns |
Looks like @kertal was right, but got snagged by a flaky "unit" test |
I was wondering if that one for sure is flakey. But I'll update from master anyway and get a new CI going. @elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
🥳 |
Updated the `Fonts` file to accept a `themeVersion` and only use the old Beta files if `v7`. # Conflicts: # test/functional/screenshots/baseline/tsvb_dashboard.png # test/interpreter_functional/screenshots/baseline/metric_multi_metric_data.png
…ets-tab * 'master' of github.com:elastic/kibana: (93 commits) [ML] Remove blank job definition as it is unused and out-of-sync with Elasticsearch (elastic#102506) [Lens] Fix wrong error detection on transition to Top values operation (elastic#102384) [ML] Anomaly detection job custom_settings improvements (elastic#102099) [Cases] Route: Get all alerts attach to a case (elastic#101878) Fixes wrong list exception type when creating endpoint event filters list (elastic#102522) remove search bar that's not working yet (elastic#102550) Migrated Ingest Node Pipeline Functional Tests to use test_user (elastic#102409) [Maps] clean up feature editing name space to avoid conflicts with layer settings editing (elastic#102516) [canvas] Refactor Storybook from bespoke to standard configuration (elastic#101962) [Security Solution] adds wrapSequences method (RAC) (elastic#102106) [FTR] Stabilize SSLP functional tests (elastic#102553) [K8] Added `Inter` font files for new theme (elastic#102359) [Workplace Search] Convert Groups pages to new page template (elastic#102449) [DOC] Add experimental disclaimer to rollup jobs (elastic#95624) [Security Solution][Endpoint] Suppress some of the jest console.error noise created by endpoint list middelware (elastic#102535) [Fleet] Improve performance of Fleet setup (elastic#102219) [Alerting] Add event log entry when a rule starts executing (elastic#102001) [Fleet] Update docker image of registry used in integration tests (elastic#101911) [Asset Management] Osquery telemetry updates (elastic#100754) Converts saved object tagging to new management layout (elastic#102284) ... # Conflicts: # x-pack/plugins/fleet/kibana.json
* [K8] Added `Inter` font files for new theme (#102359) Updated the `Fonts` file to accept a `themeVersion` and only use the old Beta files if `v7`. # Conflicts: # test/functional/screenshots/baseline/tsvb_dashboard.png # test/interpreter_functional/screenshots/baseline/metric_multi_metric_data.png * Update baseline snapshot Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
... and Updated the
Fonts
file to accept athemeVersion
and only use the old Beta files ifv7
.The EUI Amsterdam theme ships using the newest version of the Inter font family which has changed it's name from
Inter UI
to justInter
. This adds these updated font files, uses the right paths/names depending on the current Kibana themev7
orv8
.Before
After
Checklist