Hi all, we have pushed a fix to update the .css files served by the Forge bridge. It uses the @atlaskit/tokens package under the hood so this should act as the source of truth.
You could also access the tokens directly by following the ADS instructions: https://atlassian.design/components/tokens/code. (Note you can only use the tokens, the other functions will not work as expected this way)
i.e. in your Custom UI app
import React from 'react';
import { token } from '@atlaskit/tokens';
function App() {
return (
<p style={{ color: token('color.text.accent.lime') }}>Hello from my Custom UI App using Atlaskit tokens </p>
);
}
export default App;
(assuming you have unsafe inline styles enabled in your manifest.yml):
I’ve updated @forge/bridge and @atlaskit/tokens to the latest versions but I’m still not seeing the Forge issue panel use the correct surface colour when its on a raised surface. The surface colour code in the view.context has changed but the actual panel still takes the same colour.
A strange thing is if I remove view.theme.enable() and then readd it whilst tunneling into the app, the background colour is correct, but when I refresh the page its gone back to the wrong (but correct theme) surface colour.
The theme doesn’t know if your frame is on a raised surface, you’d have to set that. So in in the issue context, if your frame will be on the raised backgroupd/surface you need to explicitly set your background color.