v-dialog closes when clicking on v-text-field inside it (Vuetify) - dialog

I have a component inside a v-select , like this :
<v-select
dense
hide-details
v-model="selectedPlanFolderID"
label="PlanFolder"
:items="personPlannedFolder"
item-text="node.name"
item-value="node.id"
justify="center">
<template v-slot:append-item>
<v-divider class="mb-2"></v-divider>
<v-list-item>
<CreateNewFolderDialog</CreateNewFolderDialog>
*clickable button*
</v-list-item>
</template>
</v-select>
This is a simple component, which consists of a dialog with a title and a v-text-field to write a new name.
Once I click on the v-text-field inside the dialog(from the component), the dialog will close immediately.
I believe this happens , because once I click on the v-text, the v-select will also close (they seem to be related).
If I remove the component from the v-select , the dialog will work as expected, without closing on v-text-field click/input.
I have tried adding persistent prop to the child component dialog, but that wont work.
Is there any way to prevent this behaviour without removing the component from the v-select ?

Related

Yii2 Modal: How to change/disable layout in a Modal windows?

When you load a view in a Modal window, the view's controller's action doesn't execute. So, any code you put in there is never executed. How can i change the layout in a modal window?
I tried puting Yii::$app->controller->layout = 'popup.php'; in the view loaded in a modal, but don't. The main layout still remains in a modal window.
Also, i've tried using Yii::$app->controller->renderPartial('myUpdate', ...); in the update view loaded that call the _form in cuestion in a modal, but no way. The main layout still remains in a modal window.
So... any idea?
Ok, renderAjax() was the solution.
Thanks to me.

jqModal popup does not opens

I'm using drupal 6 form, and ahah for ajax form submit. On form submit I perform some validation and allows user to choose options that display on jqModal popup.
JS script that I'm using for jqm popup is:
$(document).ready(function() {
$("#dialog").jqm();
});
and uses tag to open the jqm popup
Choose option
<div class="jqmWindow" id="dialog">
<h2 id="modalHeading">Select one</h2>
x
<form> form values</form>
</div>
Instead of opening popup window, it changes the url by adding # at the end.
Same code is working fine on the other page of my website.
jqModal.js file is included to the page on pageload.
The default trigger is any element with a class of "jqModal", so your anchor element (Choose option) is correct and ought to show the modal when clicked.
Is anything showing up in the javascript console of the page?
Perhaps there's another javascript function that's preventing the click event from bubbling? The .click() events are assigned in a FILO (first-in, last-out) manner, so if another click event return false, the jqModal assigned event may never get called.
You can also be explicit and try;
$(document).ready(function() {
$("#dialog").jqm({trigger: false});
$("a.jqModal").click(function(){
$("#dialog").jqmShow();
});
});

How to make popUp not submit form on startup?

I am using JDeveloper 11.1.2.3.0,
I have a createInsert button that has ShowPopUp Behavior operation included. In the popUp I have inserted a form whose attributes will be clean from the createInsert operation. When I click the button the popUp shows up all right but showing an error about the mandatory fields of the form. The fields of the form of course are empty because I just opened it. So I think that the popUp is autoSubmiting the form at the starting point.
Does anyone have an idea how to stop it from doing this?
I have changed the createInsert button PartialSubmit property to false but nothing changed.
Ok found the solution. The popUp was not submitting anything actually but during the CreateInsert operation the iterator opens a new row in every related component within that page (form, table etc). So when my popUp opened up with the new form fields, a new row was being created in the back-stage in my read-only table. I changed the iterator in a new one from another Application Module for each case and everything is fine now.

How do I move a widget around on the screen?

I have a Menu widget that I want to display whenever the user clicks on specific dom elements, but I don't want a MenuBar. What's the best way to do this? I've tried attaching click handlers to the relevant DOM elements and having the click handler display the Menu, but I can only get it to display the Menu in the area where the original declarative markup would have been rendered. I can't get it to move at all. I'm attempting to use dojo.style(myWidget.domNode, 'top', calculatedTop) (and the equivalent with 'left'). What (obvious thing) am I missing?
Thanks.
Since you are using the dijit's default menu widget, I would think that you just need to specify the property targetNodeIds on the Menu Widget (reference) to define where the context menu is relevant:
targetNodeIds (Defined by dijit.Menu)
Array of dom node ids of nodes to attach to. Fill this with nodeIds upon widget creation and it becomes context menu for those nodes.
To get the popup showing on left click I believe you'd want to use the property leftClickToOpen:
// leftClickToOpen: [const] Boolean
// If true, menu will open on left click instead of right click, similiar to a file menu.
//defaults to false
leftClickToOpen: false,
Specifying this declaratively would look like:
<div data-dojo-type="dijit.Menu" data-dojo-props="targetNodeIds: ['nodeId1','nodeId2','nodeId3'], leftClickToOpen:true"
style="display: none;">
<!-- Your content here -->
</div>

How to Disable components onClick of a Button in JSF?

In my application i have three buttons, If i click on one button I have to disable all the button till the operation on that button is finished.
I dont know how to disable the other two buttons. Kindly help.
Use JavaScript to get the HTML element from the DOM and then set its disabled attribute.
document.getElementById('clientId').disabled = true;
Note that the 'clientId' is the autogenerated HTML element ID. Rightclick page and View Source to find it out. If this contains prefixes like j_id and so on, then you need to give all parent UINamingContainer components like <h:form>, <h:dataTable>, <f:subview> and so on a fixed component ID, so that the client ID doesn't need to be autogenerated anymore.

Resources