I currently have a basic form where the user can submit a paragraph of text. However, I want them to be able to choose either to paste their paragraph or to instead upload a file. In essence, this choice will determine which input field shows. Is there a mechanism to do this?
Use quill if you are looking for text editor like in most content management website
Related
I have a simple text webpage that I intend to upload to ipfs.io Once it's uploaded I won't be able to change the HTML
However I want to be update the text on the page.
How might I go about achieving this? Ideally as simply as possible.
You could use Javascript and fetch api
Full context, because I'm not exactly sure what I'm looking for:
I am working on web software, and I have various mail templates that get sent. The templates are just HTML files. I'm planning to implement a text editor so that my clients can edit these mail templates. However, there are certain 'chunks' for the files that I don't want them to be able to edit, so I was thinking of putting 'flags' of some kind into the html so that I can detect them programmatically and make the blocks un-editable in the UI.
I was envisioning something like this:
<p>
lots of text here
</p>
<blank-tag-here-that-wont-display-or-do-anything>
<p>
important un-editable text here
</p>
<blank-tag-here-that-wont-display-or-do-anything>
<p>
other text here
</p>
Is there such a tag? Or something else I'm not considering? Thanks for the help.
Have you tried using your context then parse the html tags to find the tag and make the whole block visible='false' to the html editor, this way it will not show in the editor but if the html editor has the html view capability then the user will be able to modify the tag via the html viewer.
I've create one blog using html5 and css3. I need to add new posts on that blog by clicking a button. If I'll click that button one text area has to be open and it'll have the options like adding image, video and text. For example the text area that will be used to create questions in stack overflow site. Please help me to make this one...
Regards,
Sandra
You need to use some sort of server side language. You can use PHP/ even add your theme in wordpress so that you can add required functionality
You have to use a rich text editor wrote in Javascript ( you can find some on Internet) and also, you have to write some PHP to send the the input from textarea( when click on submit or publish button) to a table in database.
Examples of rich text editors:
http://www.tinymce.com/ and
http://nicedit.com/
About the php part, you can find some examples on http://www.w3schools.com/php/.
In MediaWiki 1.22 I would like to add a section of reminder text directly above the toolbar when a user creates or edits a page. There are several extensions that preload text directly into the edit form (such as MultiBoilerplate or NewArticleTemplate, but I would like to add text directly above the edit form's toolbar.
Would $wgHooks[ 'EditPage::showEditForm:initial' ][] and $form->editFormPageTop allow me to inject my text as described above? Is there a way to avoid directly editing MediaWiki's EditPage.php file to accomplish this?
Just add your warning to the page [[MediaWiki:Editpage-head-copy-warn]].
We have a many HTML forms in our application. Corresponding link to help documentation which is prepared by the content team for each page is given at the top of the page. But this does not make sense for blind people and even much for regular users as each time they need to go to the link which opens a separate page.
How can I display help text for the input boxes with content present in different page which is relevant to the current input ?
For visually challenged users I can use "aria-required" and "aria-describedby" flags if there is a way to link to that documentation.
The help text really should be on the same page as the form. You can always use an accordion or some other method to collapse or show/hide the docs.
If the content really does have to live at a separate URL, I suppose you could make an AJAX request to the corresponding HTML page to pull the content in upon user request for it, but make sure to use ARIA Live Regions so users of assistive technology will know that the new content has been loaded.
Also, this may be helpful: WCAG 2,G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input