I am using RTE from Syncfusion in ASP.NET.
I have a problem with keyboard shortcuts and keystrokes. When I try to paste (to replace) on a selected text it does not work and does not show any error either. When I paste a large text portion in the RTE it only works if I empty it first. And after the first paste it does not allow further text after that. In some places when text is already available, it does not allow more text to be added only space.
Has it gone crazy? Tested in 3 browsers so far, Chrome, Edge and Safari.
We have checked the reported issues with RTE sample. unfortunately, we could not reproduce the issue. We have attached a video demo for your reference. Please refer to the following link for Video: http://www.syncfusion.com/downloads/support/forum/133567/ze/RTECopypaste-1148901235
We have attached a sample in the below link:
http://www.syncfusion.com/downloads/support/forum/133567/ze/RTE-541310972
Please check if the reported issue is reproduced at your end. If yes, then provide us a sample or video exhibiting the issue at your end, this will help us debug the issue locally and provide solution.
Related
I don't seem to understand what the coverage tab in the Chrome Devtools exactly means. From the documentation I found online, it doesn't become 100% clear to me.
For example:
There is a CSS file called 'jet-elements.css' on my website (see screenshot). In the coverage tab, it says that this file is 229.658 bytes (229kb). However, the network tab shows that only 21.7kb is loaded.
Screenshot of Chrome Devtools
My questions:
What's the right way of reading the data from the network and the coverage tab? What does the data from both tabs exactly mean?
What is being loaded for the user of the website? Is it the entire CSS or just the part that's used?
Does the unused CSS make the website slower for the user?
Hope someone has some answers for me! :)
We're using Barlow, available for free from Google fonts, in a web app. Here's the way a sample phrase looks when rendered on Google's example page. (If you want to reproduce it, you will need to enter the custom text yourself and adjust the slider to 14px.)
Note, in particular, the distinct space between the bottom of the i and its dot above, as well as the clarity of the top part of the f.
This is how the same phrase looks when rendered in our app, as reproduced in this Code Pen.
Note the muddy space between the i and its dot, as well as the muddy top curve to the f.
I've tried looking through all the styles on the elements in question, and I can't find any style that should affect these differently. The network tab clearly shows that the bold version of the font is being loaded; it doesn't look as if this could be faux bold.
This may seem trivial, but we've actually had quite a few complaints about how the font looks in our app, specifically that the bold, lowercase i looks like an l.
Anyone have an idea what might be happening here?
Update: Using Chrome on a Mac; I can confirm the same issue in Firefox. This is on an external display... on a retina there's no problem, as there is way more detail.
The problem turned out to be a problem with the source repo: "hinting got missed in the most recent commit" and the Google specimen (which looked correct) was "actually running an earlier version."
Happily, the maintainer was able to get the problem fixed with a subsequent version.
I am familiar with the data grid in the UWP plat form. we tried to provide the support for printing the results in sheets. we have faced the hurdles while we print the content. In the print preview panel the content looks like blurry to the view, but in the printed sheet the contents look like normal. could your share your ideas to resolve this.
Thanks in advance for your updates.
It seems it is by design.
In UWP, we use the PrintManager to inform Windows that an application wishes to participate in printing.
When we run the ShowPrintUIAsync() method, it will run the "PrintDialog.exe" that the print Preview page will be shown.
We can use the "Inspect" to test the content of the print Preview page. From the following image, we can see the content is a Image control that render by the XAML.
For the performance, it does not render as clear as the printting result. We can not change that.
If you do want this feature, you are welcome to ask on UserVoice.
I have been experiencing the weirdest problem, that I can't even begin to troubleshoot. It is important that the webpage in this project I am working is 100% printable. As you can see the signature field below and the note field (with the string "erererer") shows great in Google Chromes print preview but not when I actually print it out using the Chrome browser. In fact, the note field just prints out the border and nothing else (looks like a white empty div with a border) and the signature field prints out everything but the actual signature. When I use google chrome to save the document as a PDF and then print it out directly from the PDF everything prints perfect. When I use firefox to print, the signature area prints perfect, but the note problem remains of it only printing the outter border.
I would greatly appreciate any suggestions on how to begin to fix this or any input on why this may be happening.
Many thanks in advance!
If you need accurate & reliable printability, going iText and PDF is a solution. You can render the page as PDF and it will show in the browser, and then print exactly as specified.
HTML is often inexact, has marks (page numbers etc) from the browser, and can be glitchy.
iText (latest versions) are available open-source, or commercially. There's also an older version available free. See: What is latest version of itext that is not AGPL?
As for your note field: maybe there's something weird with backgrounds, non-standard styling? , or fonts that aren't present? Try making it a plain vanilla table.
Strange problem. Text fields in my flex simply do not work under Mac. Inputted characters do not appear within it. I do not have any specific font set (just _serif), so I don't thing it's font issue.
In what direction should I dig? Have anyone similar experience?
Try creating a completely new project with no formatting of any kind. Create a single text field and see if that shows up.
You may want to consider removing the _serif css to see if that has any effect.
See Soliant's blog for other helpful flex examples