I am using marionette version 1.2.3 and backbone version 1.1.0
Here is my UI and events hash:
ui:{
title : '#modelTypeTitle'
},
events:
{
'change #ui.title' : 'validateTitle'
},
This seems to match what the documentation says:
"You can also use the ui hash values from within events and trigger keys using the '#ui.elementName'"
To clarify I want to know why what I am trying above does not work. but the following works fine:
events:
{
'change #modelTypeTitle' : 'validateTitle'
},
Okay, problem solved after you showed version.
This feature, parsing #ui. syntax within the events and triggers hash, is recently added in 1.4.0 in early December. See changelog: https://github.com/marionettejs/backbone.marionette/blob/master/changelog.md
Just update your Marionette version to the latest stable(1.4.1 currently) and problem should be solved.
*I just noticed this new feature thanks to your question. I don't feel comfortable at this point before, now solved. Another evidence of helping others could also help the man himself. :)
Related
Per Facebook dev documentation, the share parameter "quote" should insert text:
https://developers.facebook.com/docs/sharing/reference/share-dialog/
This seemed to be working the other week, but now even using their own testing tool ( http://www.fbrell.com/Sharing/2%20-%20FB.ui%20Dialogs?fbclid=IwAR2TX_eOex-HmIqbIfz9sakxN_laCAVVW_g6p-dW54WwVZkXQ_u5VZi8OCE ), the quote parameter doesn't seem to be inserting any text into the share dialog that pops up.
Anyone else experiencing this?
Someone from the Meta team has said "the quote feature has been deprecated". The documentation had still not been updated at that time, though.
Pretty weird for them to remove a feature with no warning or update to their documentation, then call it "deprecated" (which typically refers to a feature that still works but will be removed in the future).
same problem for me
FB.ui({
method: 'share',
href: this.location,
quote: this.description
})
It worked a week ago, but now it doesn't. but the Facebook documentation does not mention anything about this change
https://developers.facebook.com/docs/sharing/reference/share-dialog
https://i.stack.imgur.com/CgSA0.png
Same problem here
FB.ui(
{
method: 'share',
href: 'https://my-url',
quote: encodeURIComponent('My quote')
}
);
I inherited a legacy website written in old zul and have to add new datebox component for birthday datepicker.
Have added a constraint to accept dates before a given date but that triggers an error alertbox from start as the date presented/selected by default on the datepicker is today.
I wouldn't want to use a workaround but to all due respect it seems like this is something over the top feature I'm looking for in zk's reality:
The main showcase for zul does include a birthday datebox, but pretty lame as it doesn't contain any constrain on age.
There is zk fiddler to show how the before constrain works, but that just proves my point that it doesn't select the first proper date for default date at least, if there is no clean way of setting it.
There is forum post that proposes a workaround to set the default year, so Zk is most probably incapable of doing this without a workaround.
There is an open ZK Jira issue from 2017 that addresses somewhat this issue, with a proposed solution pretty much the same as the workaround mentioned in the above point - so the hope is kinda lost, have to go on the workaround route.
I did try that workaround (after the forum post, as that has default year), but the workaround doesn't work for me. It does execute the
this.setValue(initialDate);
And I see that the value is set into the datebox's _pop/_value and _pop/_end nodes but no difference is visible on the datepicker box, still today is preselected altough it is greyed out - so no effect.
Still, when I try it in a fiddle with version 6.5.8.1, the oldest engine that exists, it does work, but not locally with v5.0.11.
In the buglist for this version there is no mention of datebox. Tried to look into to some bugs that might be interfering but turns out it was just another episode of me wasting time with this.
Tried in the 5.0.11 sandbox and it doesnt work with that version. The structure of how I use it is imitated in the linked fiddler. Hints on a workaround that works on this version?
ZK 5.0.11 is a bit on the older side currently, so it might not accept exactly the same overrides as later versions. If I understand the issue correctly, it boils down to either
1 - setting a value before Datebox is rendered to have a "initial date" opened in calendar.
I'd say that's the easy way out, since you can use either composing or databinding to set the value of the datebox during page rendering. Here's a small sample using databinding and zscripts, but the same logic should apply from composer with setValue(). You mentioned that this doesn't work for you locally with 5.0.11 though. Can you share the code that you are using for this? Sample code here in fiddle I can run it on local 5.0.11, and it set the date before popup is opened.
or
2 - setting an initial date (which doesn't affect the selected value) but would be the target for the opened calendar.
This is not a default ZK 5 behavior for datebox. If you want that effect, you would need to customize it using an override script. Simplest way in can think of in ZK 5 is to use the open event of the datebox popup here's an example of what it would look like (package in a script tag in a single page for the example, would use a global js file for real deployement) example here
Suddenly highcharts-ng module started throwing out quite a strange error.
I did not touch this part of the code and I don't use setExtremes property.
Error Line 92:
If somebody already faced with such kind of problem I really appreciate your help.
This is a new bug introduced in 0.0.9 and only partially fixed in 0.0.10.
It will be fixed in a 0.0.11 shortly. In the meantime if in your chart config you define a yAxis it will work:
yAxis: {
events: {}
}
The problem was with highcharts-ng version update from 0.0.8 to 0.0.10
So we decided to do the simplest solution for now and downgrade to 0.0.8.
If you know how to solve the problem with new version - please post it here.
Mootools and ExtJs have a compatibility issue when used on the same page. Mootools throws the following error :
Uncaught TypeError: Property 'id' of object #<HTMLDocument> is not a function
How can we use both frameworks side by side ? Is there a workaround ?
This looks like a document.id('..') reference issue, it is defined but it's not the mootools method...
Nothing will work if it's not pointed to the mootools method.
I would argue that ExtJS or your app has added a property id to document, which is not a function as is likely a String or another primitive.
Pretty sure that ExtJS would not have been overwriting document.id, especially given that they (Sencha) employed MooTools core team dev #subtlegradient (thomas aylott) who co-wrote the Slick selector engine and helped engineer the document.id transition in MooTools from the simple $ in 1.11
You probably cannot do document.id = $ to restore it as it's by reference and it's been overwritten.
Only chance is to try loading MooTools after ExtJS is loaded and started - or load MooTools, save a ref like document.$id = document.id; immediately after, load ExtJS and then restore it back when ready via document.id = document.$id; delete document.$id - still no guarantees this will run at the right time. you really need to see what modifies your document object in web inspector (you can add a watcher)
I've came across this issue today and I think I might need some help. We are using 1.6.1 version of Dojo, but this is cross version issue.
Steps to reproduce the following issue are pretty simple:
click the dojo doc link for Filtering Select dijit.form.FilteringSelect
On the documentation page, click the first FilteringSelect sample
In the Codeglass window sample, click the filteringselect and add "x" to "California", thus bringing it to invalid state
While focused, delete the "x" letter.
and here comes the problem. Technically the value is correct, but the dijit is still like in error state (unless it loses focus).
I'd like to get the dijit react and render correctly straightaway I delete the character causing the invalid state without losing focus.
Any ideas for the workaround?
Thank you.
ok. for eveyryone else interested the solution was 'quite' simple, just use the dijit.form.FilteringSelect._refreshState() .The underscore prefix is might not be someone's cup of tea but that was the only way to get it in correct state.
in our case it was a bit tricky as we are using the dojox.data.QueryReadStore wrapped in our own object and I needed the proper trigger which I've found in connecting to onComplete event of the inherited fetch() method.