An easy solution is to press the &lt;kbd&gt;F7&lt;/kbd&gt; key on the Chrome browser.

This method makes it easy to enable/disable cursor blinking problem.

There&#39;s an option called **Navigate pages with a text cursor** in Accessibility settings, you&#39;ll need to disable this option.

Go to `Chrome Settings ​​→ Advanced → Accessibility`, find the `Navigate pages with a text cursor` option, and disable it.

Ref. https://support.google.com/chrome/thread/77878717?hl=en

Hit the F7 key on the Chrome enable/disable cursor blinking.
You can also enable/disable in chrome setting.

Got to 

    Chrome Settings / Advanced / Accessibility &gt; Navigate pages with a text cursor option

Disable it.

Disabled this and now its not showing the cursor blinking

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/pJQov.png

I have the same problem here in all websites. 

The problem is not extensions but the Chrome browser on version 86.

I downloaded Chrome 87 beta and problem is fixed.

So wait until release version 87.

there is a way to round this issue ==&gt;

by adding this to your global.css you can avoid this blinking cursor

    *:not(input) {
      -webkit-touch-callout: none; /* iOS Safari */
      -webkit-user-select: none; /* Safari */
      -khtml-user-select: none; /* Konqueror HTML */
      -moz-user-select: none; /* Old versions of Firefox */
      -ms-user-select: none; /* Internet Explorer/Edge */
      user-select: none;
    }



I want to use Bootstrap 5 with Vue 3. As Bootstrap 5 uses vanilla JS (no JQuery), can I use Bootstrap 5 directly in a Vue 3 project (without using Bootstrap-Vue)? Can someone guide me how to use Bootstrap 5 with Vue 3?

Using Bootstrap 5 with Vue 3

This is more of a theoretical question than anything. I&#39;m a Comp sci major with a huge interest in low level programming. I love finding out how things work under the hood. My specialization is compiler design.

Anyway, as I&#39;m working on my first compiler, things are occurring to me that are kind of confusing.

When you write a program in C/C++, the traditional thing people know is, a compiler magically turns your C/C++ code into native code for that machine.

But something doesn&#39;t add up here. If I compile my C/C++ program targeting the x86 architecture, it would seem that the same program should run on any computer with the same architecture. But that doesn&#39;t happen. You need to recompile your code for OS X or Linux or Windows.(And yet again for 32-bit vs 64-bit)

I&#39;m just wondering why this is the case? Don&#39;t we target the CPU architecture/instruction set when compiling a C/C++ program? And a Mac OS and a Windows Os can very much be running on the same exact architecture.

(I know Java and similar target a VM or CLR so those don&#39;t count)

If I took a best-shot answer at this, I&#39;d say C/C++ must then compile to OS-specific instructions. But every source I read says the compiler targets the machine. So I&#39;m very confused.

Why do you need to recompile C/C++ for each OS?

As I&#39;m paranoid more with online breach, recently noticed that Google chrome elements upon click showing cursor blink and that&#39;s spooky. HTML page elements became editable?   It&#39;s not happening with Mozilla, and the extensions enabled on chrome are,
- Apollo Client Developer Tools,
- Authenticator
- Vue.JS Tools

On Firefox, it&#39;s allowing to select and no cursor blinks and that&#39;s the default behaviour.

Demo of problem:

[![GIF][1]][1]



  [1]: https://i.stack.imgur.com/jb4TA.gif

Google Chrome weird cursor blink on pages, never seen &#39;em before

As I'm paranoid more with online breach, recently noticed that Google chrome elements upon click showing cursor blink and that's spooky. HTML page elements became editable? It's not happening with Mozilla, and the extensions enabled on chrome are,
<ul>
<li>Apollo Client Developer Tools,</li>
<li>Authenticator</li>
<li>Vue.JS Tools</li>
</ul>
On Firefox, it's allowing to select and no cursor blinks and that's the default behaviour.
Demo of problem:
<a href="https://i.stack.imgur.com/jb4TA.gif" target="_blank" rel="noopener noreferrer"><img src="https://i.stack.imgur.com/jb4TA.gif" alt="GIF"></a>

I have an Angular application that I am trying to debug in [VS Code][1].

When I compile and run the application (`ng serve`) the breakpoints are bound:

[![enter image description here][2]][2]

However, when I specify a different configuration e.g. `-c qa` or `-c uat` they are unbound:

[![enter image description here][3]][3]

 1. Why are the breakpoints unbound when I specify a different
    configuration? 
 1. How do I bind the breakpoints for a debug session targeting a particular environment?

---

#### Relevant information

##### *angular.json* sample environment configuration:


```
&quot;uat&quot;: {
  &quot;fileReplacements&quot;: [
    {
      &quot;replace&quot;: &quot;src/environments/environment.ts&quot;,
      &quot;with&quot;: &quot;src/environments/environment.uat.ts&quot;
    }
  ],
  &quot;optimization&quot;: true,
  &quot;outputHashing&quot;: &quot;all&quot;,
  &quot;sourceMap&quot;: false,
  &quot;extractCss&quot;: true,
  &quot;namedChunks&quot;: false,
  &quot;extractLicenses&quot;: false,
  &quot;vendorChunk&quot;: false,
  &quot;buildOptimizer&quot;: true,
  &quot;budgets&quot;: [
    {
      &quot;type&quot;: &quot;initial&quot;,
      &quot;maximumWarning&quot;: &quot;2mb&quot;,
      &quot;maximumError&quot;: &quot;5mb&quot;
    },
    {
      &quot;type&quot;: &quot;anyComponentStyle&quot;,
      &quot;maximumWarning&quot;: &quot;6kb&quot;,
      &quot;maximumError&quot;: &quot;10kb&quot;
    }
  ]
},
```

##### Software versioning:

- [Visual Studio Code][1] `1.50.1`
- [Chrome][4] `83.0.4103.122`
- [Debugger for Chrome][5] `4.12.11`
- [JavaScript Debugger (Nightly)][6] `2020.10.2217`


  [1]: https://code.visualstudio.com/
  [2]: https://i.stack.imgur.com/iON2a.png
  [3]: https://i.stack.imgur.com/tgPA3.png
  [4]: https://www.google.com/intl/en_uk/chrome/
  [5]: https://github.com/Microsoft/vscode-chrome-debug
  [6]: https://github.com/microsoft/vscode-js-debug

Unbound breakpoint - VS Code | Chrome | Angular

Stetho and Google Chrome DevTools have become unusable after a macOS update (I doubt that macOS update is the origin of this bug, but I prefer to mention it).

Here is the appearance of DevTools after the open of &quot;inspect mode&quot; on a device (provided by Facebook Stetho library for Android &amp; OKHttp).

![DevTools window](https://i.stack.imgur.com/8AK7W.png)


There are no longer &quot;CSS&quot; stylesheets on the page and fonts have changed.
Many tab pages aren&#39;t displayed (i.e. Network Requests), I only have access to some error messages :

```
There were 84 bytes that were not consumed while processing request 4
There were 84 bytes that were not consumed while processing request 5
There were 84 bytes that were not consumed while processing request 6
Failed to clear temp storage: undefined
```

I followed instructions on this issue : https://stackoverflow.com/questions/31358446/failed-to-clear-temp-storage/35172470 and this one : https://stackoverflow.com/questions/36850053/failed-to-clear-temp-storage-securityerror-in-chrome?noredirect=1&amp;lq=1 but I haven&#39;t been able to fix the problem. 

Here is what I tried :
 - Uninstall and reinstall Chrome with AppCleaner
 - Remove chrome cache from disk
 - Remove chrome profiles from `~/Library/Application\ Support/Google/Chrome`
 - Create and use a new Chrome profile
 - Try to connect on Firefox distant debug (unfonctionnal)
 - Restart system

Have any of you ever encountered this problem ?
Thanks !



Chrome DevTools broken - Stetho unusable

When creating a react app via `npx create-react-app` and running it, a warning pops up in DevTools (Chrome 88 and 89):

&gt; scheduler.development.js:298 [Deprecation] SharedArrayBuffer will
&gt; require cross-origin isolation as of M91, around May 2021. See
&gt; https://developer.chrome.com/blog/enabling-shared-array-buffer/ for
&gt; more details.

**Environment**
```
  current version of create-react-app: 4.0.1
  running from /Users/mahdi/.npm/_npx/25767/lib/node_modules/create-react-app
  Binaries:
    Node: 14.15.4 - ~/.nvm/versions/node/v14.15.4/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.10 - ~/.nvm/versions/node/v14.15.4/bin/npm
  Browsers:
    Chrome: 88.0.4324.96
    Edge: 87.0.664.66
    Firefox: 84.0
    Safari: 14.0.2
  npmPackages:
    react: ^17.0.1 =&gt; 17.0.1
    react-dom: ^17.0.1 =&gt; 17.0.1
    react-scripts: Not Found
  npmGlobalPackages:
    create-react-app: Not Found
```

[![enter image description here][1]][1]

**Steps to reproduce**

 1. `npx create-react-app myapp` 
 2. `cd myapp &amp;&amp; npm start Open`
 3. [http://localhost:3000](http://localhost:3000) in Chrome 88 or 89, regular or Incognito mode
 4. Open DevTools: the warning is displayed

**Any suggestion for resolving this warning?**

  [1]: https://i.stack.imgur.com/0lq4e.png

SharedArrayBuffer will require cross-origin isolation as of M91, around May 2021

When I `console.log()`, the Chrome console gives the log but instead of showing the file and line number it just says `react_devtools_backend.js:4049`. How do I get the console to show the file and line number when I `console.log()`?

![screenshot of console output showing &quot;react_devtools_backend.js:4049&quot; in place of a correct file and line number][1]

  [1]: https://i.stack.imgur.com/ChxIZ.png

Why is console.log() showing react_devtools_backend.js:4049 instead of the file and line number?

**The undesired functionality**
&lt;br&gt;
In Chrome 95 there was introduced new functionality where the user can hover and click on the unit part of a css value to hotswap the unit. 
&lt;br&gt;
The feature is part of a package solution that has been labeled &quot;**Length Authoring Tools**&quot; in the release notes, and can be seen in action and described in detail in the [release notes on the official blog][1].
&lt;br&gt;
&lt;br&gt;
How can this feature be disabled?
&lt;br&gt;&lt;br&gt;
**Issue 1:**

[![enter image description here][2]][2]

If a css-line in the inspector says `padding: 0 10px;` then the user can click the `px`-part of the line and open a selector that let&#39;s the user swap `px` to other units such as `rem`,`vmax` or `in`.
&lt;br&gt;
Clicking this part of the value no longer lets the user edit the entire value quickly. Most users already know what unit they desire to use beforehand, so they do not need to be helped to accidentally select `pt` or `vw` when working exclusively with `px` everywhere else.
&lt;br&gt;&lt;br&gt;
**Issue 2:**
&lt;br&gt;
[![Ctrl+C][3]][3][![After Ctrl+V][4]][4]
&lt;br&gt;
When selecting and copying properties from the inspector there is now inserted whitespaces/new lines between the value and the unit since the unit portion seems to be considered a separate element. This makes prototyping in the devtools and copy/pasting to external documents very tedious and broken.


  [1]: https://developer.chrome.com/blog/new-in-devtools-95/#length
  [2]: https://i.stack.imgur.com/dq3KE.png
  [3]: https://i.stack.imgur.com/bbESR.png
  [4]: https://i.stack.imgur.com/RvRNP.png

Disabling the &quot;Length Authoring Tools&quot; (css unit selector) in Chrome Devtools Inspector

With regard to the [Log4j][1] [JNDI][2] remote code execution vulnerability that has been identified [CVE-2021-44228][3]  - (also see references) - I wondered if [Log4j-v1.2][4] is also impacted, but the closest I got from source code review is the [JMS-Appender][5].

The question is, while the posts on the Internet indicate that Log4j 1.2 is also vulnerable, I am not able to find the relevant source code for it.

Am I missing something that others have identified?

Log4j 1.2 appears to have a vulnerability in the [socket-server][6] class, but my understanding is that it needs to be enabled in the first place for it to be applicable and hence is not a passive threat unlike the JNDI-lookup vulnerability which the one identified appears to be.

***Is my understanding - that Log4j v1.2 - is not vulnerable to the jndi-remote-code execution bug correct?***

### References

 * *[Apache Log4j Security Vulnerabilities][7]*

 * *[Zero-day in ubiquitous Log4j tool poses a grave threat to the Internet][8]*

 * *[Worst Apache Log4j RCE Zero day Dropped on Internet][9]*

 * *[‘Log4Shell’ vulnerability poses critical threat to applications using ‘ubiquitous’ Java logging package Apache Log4j][10]*

This [blog post from Cloudflare][11] also indicates the same point as from [AKX][12]....that it was introduced from Log4j 2!

**Update #1** - A fork of the (now-retired) apache-log4j-1.2.x with patch fixes for few vulnerabilities identified in the older library is now available (from the original log4j author). The site is https://reload4j.qos.ch/. As of 21-Jan-2022 version 1.2.18.2 has been released. Vulnerabilities addressed to date include those pertaining to [JMSAppender][13], [SocketServer][14] and [Chainsaw][15] vulnerabilities. Note that I am simply relaying this information. Have not verified the fixes from my end. Please refer the link for additional details.


  [1]: https://en.wikipedia.org/wiki/Log4j
  [2]: https://en.wikipedia.org/wiki/Java_Naming_and_Directory_Interface
  [3]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228
  [4]: https://dlcdn.apache.org/logging/log4j/1.2.17/log4j-1.2.17.zip
  [5]: https://github.com/kikonen/log4j-share/blob/master/src/main/java/org/apache/log4j/net/JMSAppender.java
  [6]: https://github.com/kikonen/log4j-share/blob/master/src/main/java/org/apache/log4j/net/SocketServer.java
  [7]: https://logging.apache.org/log4j/2.x/security.html
  [8]: https://arstechnica.com/information-technology/2021/12/minecraft-and-other-apps-face-serious-threat-from-new-code-execution-bug/
  [9]: https://www.cyberkendra.com/2021/12/worst-log4j-rce-zeroday-dropped-on.html
  [10]: https://portswigger.net/daily-swig/log4shell-vulnerability-poses-critical-threat-to-applications-using-ubiquitous-java-logging-package-apache-log4j
  [11]: https://blog.cloudflare.com/inside-the-log4j2-vulnerability-cve-2021-44228/
  [12]: https://stackoverflow.com/users/51685/akx
  [13]: https://cve.report/CVE-2021-4104
  [14]: https://cve.report/CVE-2019-17571
  [15]: https://cve.report/CVE-2022-23307

Content Type	Original Author	Original Content on Stackoverflow
Question	Arun Panneerselvam	View Question on Stackoverflow
Solution 1 - Google Chrome	pano	View Answer on Stackoverflow
Solution 2 - Google Chrome	SpritsDracula	View Answer on Stackoverflow
Solution 3 - Google Chrome	Adnan AdDY	View Answer on Stackoverflow
Solution 4 - Google Chrome	muTheTechie	View Answer on Stackoverflow
Solution 5 - Google Chrome	Cava	View Answer on Stackoverflow
Solution 6 - Google Chrome	madsadi	View Answer on Stackoverflow

Google Chrome weird cursor blink on pages, never seen 'em before

Google Chrome Problem Overview

Google Chrome Solutions

Solution 1 - Google Chrome

Solution 2 - Google Chrome

Solution 3 - Google Chrome

Solution 4 - Google Chrome

Solution 5 - Google Chrome

Solution 6 - Google Chrome

Why do you need to recompile C/C++ for each OS?

Using Bootstrap 5 with Vue 3

Attributions