Anton Gilgur
Anton Gilgur
> We might need to add a prop for the canvas's [`contextAttributes`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement/getContext#contextattributes) Looks like upstream enabled the same: https://github.com/szimek/signature_pad/pull/761#issuecomment-1986951356
> @agilgur5 refer to `signature_pad` that it's fixed there, but it's useless for this package [react-signature-canvas](https://github.com/agilgur5/react-signature-canvas). It is not updated I'm very aware of that, that's why this issue is...
See detailed discussion in #68 with regards to updating. https://github.com/szimek/signature_pad/issues/308 was released in `v3.0.0-beta.1`, and per the discussion above, v3 never came out of beta and v4 was just _recently_...
[Any updates](https://justinmayer.com/posts/any-updates/) [would be in the thread already](https://sindresorhus.com/blog/issue-bumping). The changes are breaking in multiple ways, including ways not really known by one of the maintainers per #68, and no one...
Ok so I was thinking changing the `on` and `off` methods to work differently for mobile, i.e. detect the `orientationchange` event instead of `resize`, but apparently that's been [deprecated](https://developer.mozilla.org/en-US/docs/Web/API/Window/orientationchange_event), as...
This would also need some tests before it could be merged
> as of March 2023 That's pretty recent though, so we'd still need a fallback for unsupported browsers 😕
If I'm not mistaken, that sounds like correct behavior. Can you provide the Workflow after you submitted it? I'm pretty sure it would only have one parameter at the top-level....
> Yes, it does show only the one parameter in the top-level of the Workflow that is run. Ok, that would confirm that this is correct behavior. > For us,...
> If you retry the workflow and override a parameter that was originally specified, Argo will not use the defaults. Wouldn't that be expected? (as the definition of an override)....