13 Aug 2007
Link to this post
06 Sep 2013
in reply to
Yes, it's very flexible when you know what you're doing as I said before.
But since a navigation widget is a cornerstone widget of every page and not an obscure or expert only widget it should be usable for people who don't fully understand the yanking and deleting of scripts and styles as you so eloquently described it.
There isn't a single template that involves themes+css+js in Sitefinity precisely for that reason.
If someone changes something where they shouldn't, regardless of which template, they can revert to a default one.
Grab any widget and revert to a default template and while the widget may not look good, it doesn't break the page. When someone reverts the navigation widget to default it has the potential to break the page due to the JS and theming.
All I suggested is for Telerik is to remove the stuff that can break an entire page (and not just the widget).
Secondly I asked if it would be possible to not bloat a mobile page by marking up and rendering the entire same menu twice. Mobile is all about a small footprint. So while I'm yanking and deleting to use a more optimal solution each time,
is it really that ridiculous to ask them to look at a better mobile suited approach out-of-the-box as well?
So again I'm not complaining, I'm not saying its a bug, I'm not saying they should.
I'm leaving it up to the Telerik team to decide if the suggestions are useful.