I am using Geb 0.9.0. I recently found out about Geb's template options. I think that they can be very useful. But I want to use them after changing a few defaults across all my Pages. I want the wait parameter to default to true.
I tried reading the whole documentation for the options but couldn't find anything about how to change the defaults.
It's not currently possible to change the defaults of template options. Please feel free to submit an issue in the tracker if you would like to see it implemented in the future.
Nevertheless even if it was possible, I would suggest not using true as the default value for the wait option because it would make any failure caused by a missing element to be delayed by the amount of time defined in the default waiting preset. Also, resolving definitions for which element is not present will result in a delay.
Related
Not sure if someone else came across a similar issue before. When I create a remote config parameter and choose it as a boolean with no conditional values. In my iOS project, firebase can read it correctly. However, when I start using conditional statements, where it is checking if the user is in a particular location e.g. UK in the image below.
When setting up this param, I did the following:

Every time I am accessing the “test_country” parameter, it is showing me the default value of false, rather then the expected “true”. I looked through different questions on stack overflow and set
configSettings.minimumFetchInterval = 60
in debug mode to fetch quicker then the recommended 12 hours in production and ever tried another stack overflow recommendation of setting the
remoteConfig.fetch(withExpirationDuration: 0)
to zero, to force fetch from remote . Just to ensure its not a fetching issue.
Any suggestion what could be going wrong? I'm not sure what more information is needed to help in this case, please let me know.
I've looked through the following questions:
FirebaseRemoteConfig fetchAndActivate not updating new value
Firebase Remote Config fetch doesn't update values from the Cloud
And many more, even posted the question on Firebase slack page.
This issue has been resolved. With the information I currently gave, it was probably going to be hard to deduce what went wrong. Apologies for anyone that read this question.
On to the answer. For my app we have a release build and a debug build. Only one firebase to manage them. So, for debug build, we normally turn off:
FIREBASE_ANALYTICS_COLLECTION_DEACTIVATED
For more information on this see this link -> Configure Analytics data collection and usage
This needs to be turned on, in order for Google Analytics offers to control the collection and use Analytics data. Which I believe is required for conditional statements. Especially if the conditional statement is using a custom definition.
I use Vaadin7 and I develop my application and test it with Edge. When I enter information in my input fields, I remark than Edge store data like this (see screenshot). My question is can we block with Vaadin the message in my input fields ? I don't want change parameter in my browser Edge but I would like to do it in my code.
Best regard.
Thank you
Screenshot
It's a tad complicated.
First of all, there is no standard way of doing this. There is the non-standard attribute autocomplete that, when set to off, seems to work (or at least have worked at some point in time, see Disable browser 'Save Password' functionality) but only in non-edge browsers. One trick seems to be to use some kind of hiding/obfuscation (which I would consider a bad idea and probably leads to accessibility issues) like mentioned here: https://stackoverflow.com/a/2555771/10493440. A current approach is using invalid data: https://stackoverflow.com/a/52608082/10493440
I would not suggest any of that as it might break at any time without warning. Changing your browser's setting is the proper way to go even if that might feel unsatisfactory.
For the Vaadin part: Give your field an ID and then apply any of the suggestion above via JavaScript.execute(...) method.
I'd like to perform operations like automatically update a field based on another field's value (for example if the assignee field is empty automatically assign to a default, set an hidden "due date" field based on the release-fix start date, ecc.) or write a custom validator that does validations based on a combination of values.
Every time I go searching on the jira forum I find java fragments of code, so everything seems to be possible, but it seems it is only at one condition: to buy the script runner plugin!
It seems strange to me: of course this plugin seems to be doing a lot of boilerplate for you but...what if I want to make a little more effort but still not payng for something that, in my opinion, should be free? I'm already paying the software license...isn't there another way to perform such post actions?
Try MyGroovy. It provides similar features. For tasks like execution post-functions I suppose it would fits good.
We've noticed a very strange behavior change on our website (asp.net MVC) starting early morning (GMT) on the 12'th of January this year (2018).
Http POSTs from the site started firing twice (unconfirmed, but we suspect sometimes more than twice), and scouring high and low we couldn't find that we'd changed anything.
One of the few things we dynamically load is Google Analytics (specifically Google Tag Manager), and in the course of trial-and-error we tried disabling everything external (which made the phenomenon disappear) and then re-enabling them one-by-one, once we came to re-enabling GA the problem re-appeared.
We also tried removing everything except GA and the problem persisted.
When searching we can't find that anything has been updated in GA, so it's very unclear why it suddenly started, and we have also been unable to find anyone else reporting the same problem (either historically or presently).
Our current best guess is that one of GA's dependencies have updated, and either it contains a bug, or it's exposing an already existing fault in our code.
Has anyone else noticed the same problem? Anyone find something in their code that caused the strange behavior of GA?
I found the error, it was caused by two erroneously set up triggers.
Both triggers were form submit type, and both had double activators, one "Activate trigger when all conditions are met" and one "Activate trigger on specific forms".
The problem was that both "all conditions" activators were set to "url matches regular expression .*", where as the second activator for both targeted a correct Form Path for each respectively.
Whoever set it up must have assumed that Google Tag Manager was using a logical "and" between the two activators (not an unrealistic assumption), but based on my testing at least it seems that the trigger activates on either activator matching.
I couldn't see any reason for the first regex match towards ".*", so the fix was to simply supply a unique url expression for each trigger.
No explanation yet as to why it suddenly became a problem, because the configuration has been wrong for a couple of months at least.
P.S. For whatever reason our GTM is not in English, so take my quoted names on fields/etc with a grain of salt as they are translated.
Update
The website uses ajax to post the forms, the combination of that and the "Await tags" flag on the triggers are looking as likely sources of why the combined conditions were not acting as expected.
Which means a non-announced performance-update to GTM regarding "Await tags" could have been the catalyst which caused the problem to start occuring with alarming frequency.
I need to know how to use each and every attribute of Struts2 tags. I
have gone through all possible websites by searching via Google, But
no one has understandable explanation or examples of each and every
attributes of each struts2 tags.
for example: In "optiontransferselect" tag, for
allowAddAllToRight attribute I have no idea what String do I need to give for it.
here is one of the site I refered...
If you want to understand every single option, do two things:
Use every single option.
Read the source code.
When something is listed as "enable", it's almost always a true/false value, as it is in this case. Why it's listed as a string, not sure; either an issue with the annotation processor, or it was added and the type conversion was done manually, or...?
While I (sort of) understand the motivation for wanting to understand "each and every attribute" of each tag, IMO your time would be better spent learning more important framework details.
I am afraid you will find them at anywhere as these attributes have been defined and provided based on generic needs and its quit possible that some one need few of them and some need others.
i even never used all of the tag properties and in most of the cases we end up using few as per our choice.
If you want to find what each and every property/ attribute making end effect best way is to create a demo struts2 application pick up few tags go to struts2 tag reference page read there description and start playing with them and see how things are changing and check generated HTML code.
There is no other shot-cut for this.
But why you need to know all the properties? i am just curious
Struts2 tag refrence