I can't be 100% certain, but having recently upgraded to Big Sur it now appears that the Vaadin rich text editor component (PRO) no longer works fully when using a Safari browser.
When attempting to highlight some entered text and setting it bold/italic/underlined or creating a hyperlink, the cursor jumps to a different position in the text and some other control buttons are highlighted (e.g. text alignment).
The same behaviour is not apparent when using a Firefox or Chrome browser under Big Sur.
Is there some special treatment now required for Safari, or is it a bug in Vaadin that the new version of safari has surfaced?
Thanks.
Yes, that's a known issue that is currently investigated, see https://github.com/vaadin/web-components/issues/2115
Related
I'm using embed to embed a pdf into my web page. I could also use object or iframe. I want the pdf to open full width of the page, which i have working. But I want the zoom level to be "Page Width". Ive seen several solutions for height, like #view=FitH and some for specific percentages, but not "Page Width"
Most PDF settings are browser specific and subject to user control so here a Chrome based Edge (on the left) and a Firefox based clone (on the right) the biggest problem noticed in these four types of loading is the lack of object support (totally missing in bottom right). Note:- I have security set so only the high speed secured Firefox based plugin viewer will show me PDFs inline without risk of running a script.
However in direct answer to the question not all browsers support the acrobat#tags but most will attempt #zoom=50% (and #page= except perhaps Safari?) whereas fit has frequently been an odd behaviour difference between all of the camps. I show the chrome result below.
the correct tag could be #FitW and that's what I used when chrome unsecured viewing is turned on
I wanted to make Intellij IDEA on windows look like the one on OS X Because in
my opinion it looks much better, so I installed MacType, I was able to get the
editor font render correctly, but when I change the UI font to match OS X's UI
font, The text gets cut off in some places. The font I am trying to use is
Lucida Grande size 15. You can see it for yourself in the picture
below:
Intellij UI Text getting cut: https://i.stack.imgur.com/4jnda.png
But if I remove disable MacType rendering, everything works fine, but it looks bad.
Intellij UI Text without MacType rendering: https://i.stack.imgur.com/AJEUl.png
I've tried changing MacType's settings, but nothing works!
I am on Windows 10 Creators Update with Intellij IDEA 2017.2
Any help would be appreciated.
I found the answer myself! Apparently if you open the mactype profile you are using with notepad, and paste the following text at the end of the file:
[Experimental#idea64.exe]
ClipBoxFix=1
Then all the fonts will render correctly. Note, this does not only work for Intellij IDEA, but also all other java applications and a few others. To achieve this, all you have to do is replace "idea64.exe" with the name of the app executable. An example is for the 32-bit version of Intellij, you would replace "idea64.exe" with "idea.exe".
More information can be found here: https://github.com/snowie2000/mactype/wiki/ClipBoxFix
I have a PDF that is generated with PDFlib that has fillable fields. They work as expected on Chrome, FF, Edge, IE, but not on Safari.
We have no Macs at work, so I'm looking at this using SauceLabs with OSX El Capitan, Safari 9.3 on 1376x1032 resolution.
When I fill out the fillable field on a form such as https://www.pdflib.com/pdflib-cookbook/pdf-on-the-web-server/starter-webform/php-starter-webform/ in-browser (again, Safari only), when you click outside the fillable field, the text moves up a couple of pixels. Click to edit again and it regains its original position. Click outside and it moves up again.
Is this an unavoidable Safari bug or is there anything I can do to prevent this from happening (currently reading the PDFlib documentation, and I have seen nothing that remotely mentions this)?
They work as expected on Chrome, FF, Edge, IE, but not on Safari.
please get in mind, all browsers have in the moment only limited PDF viewing support. (they are getting better and better with each versions, but they are not yet perfect)
Please use for viewing PDF files the PDF reference product Adobe Acrobat (Reader). Also other PDF viewers like the Apple Preview are not feature complete and might not display everything correct.
When it display correctly in Adobe Acrobat Reader, you know the PDF is fine and it's a bug in the viewer you use.
Couldn't decide if this is a question better for Stack Overflow or Superuser, haven't got any bites on Superuser yet...
I have Adobe Acrobat 9.0 Pro, and with that, the Convert Web Page to PDF button that displays in IE. We use this at work to review web pages and comment/markup for changes, etc.
When I use it on a web page that is responsive (such as http://microsoft.com) the resulting PDF shows the page laid out as if the browser window was sized down, but then it stretches all the elements to fit the width of the PDF.
Does anyone know if this is because of the rendering engine the Convert button uses? The resulting PDF looks a bit similar to how the page would look in Quirks mode in IE9 (using F12 developer tools and choosing Quirks mode from the Document Mode drop down.) Thanks for any help!
Anyone know why the PDF controls normally available when displaying a PDF in Safari would be missing when displayed in an iframe? Neither the "hover" controls or the extnded contextual menu is available. Safari reognized it as a PDF because the contextual menu includes the word PDF in the Open commands, ie. "Open PDF in new Window"
Opening a PDF into an empty browser works fine. The built in controls in Chrome and Firefox are there as well and work fine.
I am serving the PDFs using a very simple web page with an iframe inside a div.
I could be wrong but thought that they were there when I first started this project but I just noticed today that they are missing. Without them, PDF drawings cannot be zoomed in and out rendering them useless as PDFs.