Hi Hugo,

You probably never saw it yet but Jewel style setup is a little different
and is structured in a sass build. So I think you don't normally make
changes in defaults.css directly, because it will likely get overwritten
next time the sass build gets run. I will check this later today and
confirm... just in case I am wrong (it has been some time since I worked
directly on Jewel stuff)






On Sun, 5 Dec 2021, 11:33 pm , <hugoferre...@apache.org> wrote:

> This is an automated email from the ASF dual-hosted git repository.
>
> hugoferreira pushed a commit to branch develop
> in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>
>
> The following commit(s) were added to refs/heads/develop by this push:
>      new a458681  Fixed the brackets position according to Royale best
> practices
> a458681 is described below
>
> commit a458681985b31c6f9c8c7b62b87978d8b8e33178
> Author: Hugo Ferreira <hferre...@solidsoft.pt>
> AuthorDate: Sun Dec 5 10:33:29 2021 +0000
>
>     Fixed the brackets position according to Royale best practices
> ---
>  frameworks/projects/Jewel/src/main/resources/defaults.css | 12
> ++++--------
>  1 file changed, 4 insertions(+), 8 deletions(-)
>
> diff --git a/frameworks/projects/Jewel/src/main/resources/defaults.css
> b/frameworks/projects/Jewel/src/main/resources/defaults.css
> index 7eddae9..cd85807 100644
> --- a/frameworks/projects/Jewel/src/main/resources/defaults.css
> +++ b/frameworks/projects/Jewel/src/main/resources/defaults.css
> @@ -576,24 +576,20 @@ j|VirtualComboBoxPopUp {
>    content: "\200b";
>  }
>
> -.first.jewel.list::-webkit-scrollbar
> -{
> +.first.jewel.list::-webkit-scrollbar {
>      display: none;
>  }
>
> -.first.jewel.list
> -{
> +.first.jewel.list {
>      -ms-overflow-style: none;
>      scrollbar-width: none;
>  }
>
> -.middle.jewel.list::-webkit-scrollbar
> -{
> +.middle.jewel.list::-webkit-scrollbar {
>      display: none;
>  }
>
> -.middle.jewel.list
> -{
> +.middle.jewel.list {
>      -ms-overflow-style: none;
>      scrollbar-width: none;
>  }
>

Reply via email to