Hi, I have an existing Dojo (1.16) application. I'm adding Vue on top of it and actually almost everything works with a bit of synchronization between AMD parsing on Dojo's side and component rendering on Vue's side. There's one big issue though: TabContainer renders completely off.
Is there anybody with experience with this combination of libraries? Or any other which also exhibits similar behaviour?
with "completely off" I mean that the hidden elements from the top bar - which are correctly hidden in the version which doesn't wrap the DOM in Vue - are showing as part of the page with the version which uses Vue.
btw, I'm using Vue only for state management and routing in the client side app (for now).
Dijit is still very much the most professional looking widget toolkit out there, IMO.
hi. In the Vue+Dojo integration that posted about on Wednesday, the "dojo/ready" function doesn't work anymore. Does anybody have experience hacking into the dojo/ready mechanism and running the queue when the app is "ready"?
I would like to ask you if somebody could hint me to github source or some documentation where I could find any information about usting relative paths (not component names in define) in data-dojo-type how they are being resolved. I noticed in some cases that they're not resolved relatively to the js component / file which is using that html template. Sometimes it's being resolved in context of dojo/parser module which is very confusing to me.
I know that using relative paths is not the brightest idea in html templates but unfortunately that's not the code I can change too much.
Unfortunately no. I noticed in some propertiary code that "../../shared" something like this works for the 1 component and doesn't work for 2 component even though they're referencing the same component and they're in the same directory
@dylans: hi! I've submitted a PR to address CVE-2021-23450. Could you have a check and comment as to whether you think it's the correct fix?
I'd be happy to backport the same fix to whatever other versions you'd like to release.
@dylans Is there going to be an update to release the fix for the CVE-20210-23450 vulnerability?
Looks like Chrome is going to remove some deprecated stuff from navigator, such as userAgent and appVersion. This is used by dojo/sniff.js and a few other places. Will dojo break because of this? Should there be an update to fix this?