Javascript Prompt() text is partially hidden in Internet Explorer 11 -

-

I am trying to display the "Normal than normal" text in a prompt () box. While calling the Javascript prompt () function in Internet Explorer 11, a large part of my text is hidden. It seems that only 2 rows of text are supported. Chrome, Firefox and Opera are working just fine. It's just an IE problem is.

Here is a bella that shows the problem: 

  Prompt ("Lorem Ipsum is the only dummy text of the printing and type-sitting industry since the 15th century, Lorum Ipsum is the standard dummy text of the industry, when an unknown printer installed a type of galley and was framed for making a type of sample book, it is not left for only five centuries, but there is a leap in electronic typeetting too, Essentially a Reversed balance. In the 1960s, with the introduction of Letraset Sheet with the Larsem Epsom route, and more recently, desktop publishing software such as LL.D. PageMaker was popular with versions of Lorem Ipsum.);

I'm only able to see this lesson " Lorem Ipsum is the only dummy text of the printing and typesetting industry. Lorem Ipsum has been the standard dummy text of the industry since 1500, when ". The rest is not displayed.

I am afraid that I already know the answer, but why? I like to use the prompt () and do not want to use custom modals.

The fact that you should not use window.prompt is the fact that due to this thread block it is largely frowned, and thus its application Today the web has moved on to use the asynchronous nature of JavaScript; it should be away from things like warning , soon , etc. Prompt is not supported in the immersive Internet Explorer ("Metro"), Internet Explorer on the Xbox, or Windows Web App (formerly Windows Store app). Instead, you need these types of needs Area third-party tools and libraries (such as Bootstrap, are encouraged to take advantage of jQuery UI, etc.).

All this is being said, this is a real difference between Internet Explorer and other modern browsers, and as a result I have opened an issue to discuss the IE team internally.


Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more