I agree with Korbinian!
Windows users are saints! They decided themselves to spend their live in
suffering! (don't confuse with surfing!) :-)
On Fri, Jan 25, 2019 at 9:29 AM Korbinian Bachl <
korbinian.ba...@whiskyworld.de> wrote:
> Option 3:
> 1) wait for MS to apply the switch to the chromium
I'm afraid there are some cases where user have no choice: corporate
Windows machine with no ability to install alternative browser :(
On Fri, 25 Jan 2019 at 14:29, Korbinian Bachl <
korbinian.ba...@whiskyworld.de> wrote:
> Option 3:
> 1) wait for MS to apply the switch to the chromium engine
Option 3:
1) wait for MS to apply the switch to the chromium engine (ditching the current
edge engine completely - see:
https://www.computerworld.com/article/3325333/web-browsers/with-move-to-rebuild-edge-atop-googles-chromium-microsoft-raises-white-flag-in-browser-war.html
)
2) relax while
Hello @Devs,
I was able to reproduce the issue, and I believe it can be fixed if we will
Option 0:
1) provide PNG instead of SVG
Option 1:
1) check if embedded web font exist using JS
2) if not will insert PNG image of SVG currently being used
Option 2:
1) modify SVG to have circle and crown
Yes I discovered :(
Thanks for the info..
On Thu, Jan 24, 2019 at 2:35 PM Emond Papegaaij
wrote:
> This is not something we can fix in Wicket. Dependency management is not
> transitive over dependencies. Wicket already manages commons-io at version
> 2.5. To fix this error, you'll need to
This is not something we can fix in Wicket. Dependency management is not
transitive over dependencies. Wicket already manages commons-io at version
2.5. To fix this error, you'll need to manage the version of commons-io
yourself.
Best regards,
Emond Papegaaij
On donderdag 24 januari 2019
Sorry for the short mail, just saw this.. Should I create a task / bug for
it in jira?
Dependency convergence error for commons-io:commons-io:2.2 paths to
dependency are:
+-dk.netdesign.ccadmin:ccadmin-frontend:3.0.0-SNAPSHOT
