Isaac Lyman
Isaac Lyman
:+1: I am having this problem as well. The `containment` property tends to put the item I'm dragging around in the wrong place. I'm using several relatively-positioned `div`s with zero-height...
I'm getting the warning as well. It's preventing JavaScript remote debugging from working in the iOS simulator, the whole app crashes when I try to use it with remote debugging...
Is there a similar example for `actionSanitizer`? This is the furthest I've gotten: ```typescript actionSanitizer: (action: S): S => { if (action.type === 'LOAD_DATA') { action.data; // TypeScript compiler throws...
Update: I've got it working with the following: ```typescript actionSanitizer: (action: S & {payload: any}): S => { if (action.type === 'LOAD_DATA') { action.payload; // This works } return action;...
@alfa-jpn I believe you tagged me by mistake.
Also: there's no way to skip the breadcrumb for a componentless parent route. If you have the following configuration: ```typescript const routes: Route[] = [ { path: 'jobs', data: {...
@jacquie do you have the link handy to where you found that information?
Update: as a workaround, I tried adding a `(click)` handler to the `` element. This doesn't seem to work.
> Want to check out this stackblitz and see what you think of this workaround? I couldn't get Stackblitz to load, but that looks very similar to what I ended...
I'm seeing the same behavior. Can mix and match `` and `` as well, it's always the same story: fonts are properly displayed in whichever instance comes first, and later...