Compatibility warning panel

What do you want to see in Hype?

Is there a way we could have a panel that displays all elements in a Hype project that may have browser compatibility issues? The current warning icons are very helpful, but in larger or more complex projects, it would be great to have all potential objects/elements/effects that could be problematic - in one panel?

Maybe something like this to give you a quick rundown of potential issues? Instead of only seeing the warning icon when physically selecting an object.

Have you found a workaround for this problem?

Testing, re-testing, more testing, attempting to bargain with God, more testing.

Are there examples of other apps with this feature? Or, have you seen examples of this elsewhere on the web? (Please include a URL)

Not that I'm aware of

How high of a priority is this for you?

[ X ] Nice to Have
[ ] Important
[ ] Can't use Hype without it

1 Like

Thanks for the feedback and mockup!

The default is to show all browser compatibility warnings in a panel at export time. Make sure that you have "Show browser compatibility warnings before exporting" checked in Hype's general preferences. Note that the little arrow will take you to the offending element.

While it would probably be nice if we have a way to invoke this without starting an export, I'd ask if there are reasons you favor it in the inspector vs. as a bigger sheet like this?

Thanks!

I would like to avoid another icon up there, it's already fiddly enough to click on them. How about a preflight type workflow? So if you enable preflight (known from print workflows) for a project or general, you get this dialog when you export. Not sure if that makes sense.

1 Like

Can you clarify how it might be different than the current feature? Thanks!

1 Like

Totally! It is just that, isn't it… :wink:
I just have it turned off.

1 Like

In fairness, there's no other way to get at this sheet than having the preference on, and it would be great if somewhere we had a full count of compatibility issues, like in the document inspector where the per-document warnings are setup.

(The main reason why this was not done initially is that it requires one of the hardest problems in computer science: proper cache invalidation :stuck_out_tongue_winking_eye:)

1 Like