Emin Gencpinar’s Post

Good morning! 😊 If you're new to JavaScript and you're not sure about the concepts of Web Storage - Cookies, Local Storage & Session Storage, this blog might help you. Give it a try! 🌻 https://lnkd.in/ddBUh4vk

Accessibility Tip of the Day 100: Don't open links in a new tab by default. This is sometimes a controversial opinion, but here's the reasoning: We should default to giving users control over how they want to open the link. If they click normally, the link opens in the same tab. If they Command+click or right-click to use the context menu, they can choose to open the link in a new tab. But, if in the code we add the target="_blank" attribute, the user no longer has a choice, and the link always opens in a new tab. If you do decide to make links open in a new tab, it's important to indicate to the user what will happen. This is usually achieved with an icon next to the link and some screen-reader-only text that says "opens in a new window". This still takes away the user's choice, but it does at least warn them in advance. Finally, every rule has exceptions. An important exception to the rule here is that if opening a link in the same tab would cause the user to lose form data or lose progress in some task, then you SHOULD open the link in a new tab. This is commonly seen for links to help pages when filling out a form. (As a bonus, here’s a great article on the topic: https://lnkd.in/g73cAafX) #accessibility #a11y #accessibilityTipOfTheDay

Ever thought about how much data you can store in LocalStorage? Neither have I, until today. For reasons I will not elaborate at present (its a surprise), I want to store an array of string values in LocalStorage. However, values stored in LocalStorage "are always in the UTF-16 string format, which uses two bytes per character" [1] so it will be necessary to convert the array into a JSON string. There is also a limit of 5MiB that any origin can use for LocalStorage [2]. So, 5MiB = 655360 bytes = 327680 chars. Assuming each string entry is roughly 15 chars (including chars the JSON stringify call adds), then I can store an array of just over 21 000 strings. So today I learnt 2 things: 1) LocalStorage is larger than I thought 2) The Mozilla developer docs are quite good. [1] https://lnkd.in/djwxut4a [2] https://lnkd.in/daXvqb9E

Your website is using Semantic Elements correctly !! A semantic element clearly describes its meaning to both the browser and the developer. https://lnkd.in/gzWVE2Qy

It’s time again for this week’s #weeklytechterm Browser Cache A browser cache is essentially storage. Your browser (Chrome, Edge, etc.) uses this storage to keep some downloaded data from each of the websites that you visit. This data is stored in the cache temporarily so that your browser can access it should you visit the same webpage in the future. Why does this data need to be stored? Well, browsers make a basic assumption – the internet is slow. Because websites will reuse certain aspects like logos between webpages. The cache allows the browser to download the logo once, store it in the cache, and display that logo anywhere that it shows up on a website instead of downloading the same thing over and over again. This helps cut down on slow page loading. Now I am sure that you have heard before to “clear your cache” when you have issues with certain webpages displaying incorrectly. Not to get into the nitty-gritty of why clearing the cache can solve issues, but basically, there is only so much space for things to be stored, and some data must be removed to make room for new data. Sometimes, the cache just gets confused with all the data shifting in and out of it. By clearing your cache, your browser must freshly download all the elements of a website, which clears the confusion. Thus, clearing your cache is a great first diagnostic step when you run into any issues with your browser. 

Do you want to learn? How Internet and Web Browser Works 💡 You can read more 👇 The web browser or internet browser has two main elements, the front-end, the user interface we interact with, and the back-end, which is invisible but essential for rendering and generating the webpage. The browser needs the web address known as Uniform Resource Locator (URL) to receive and render the website elements for generating the web page. #SolutionsFixes #BrowserHow

#Google has #updated its #crawler documentation to reflect a new user agent string for GoogleProducer, ensuring it matches the actual value being used. The updated user agent string is: GoogleProducer; (+https://lnkd.in/d83ma2_u). Website owners, developers, and webmasters should take the following steps: Review and update any custom server configurations or security rules that reference the GoogleProducer user agent. Update bot detection systems and analytics tools to recognize this new user agent string. Notify your development and IT teams to ensure all systems are adjusted accordingly. Though this update may seem small, it highlights the importance of staying up to date with Google's crawler documentation and behaviors, as these changes help ensure transparency and accuracy for the web development community.

This a nice blog, explaining what happens inside the browser when you do a navigation, basically when you enter some text in the address bar. This is part 2 of the Inside Chrome browser series, so it shows how processes and threads communicate when you start doing any navigation. As mentioned in part 1, everything outside a tab is handled by a browser process, so it has threads like UI thread which handles drawing input box and buttons, and network thread to handle the network stack and to get data from the internet, and more. The blog shows how when you enter something in the address bar, the UI thread first checks if it's a query to send to a search engine or a URL of a site you requested. If it's a site, it starts a network thread and starts showing a loading spinner in the place of the site favicon. It shows how if a server responds with a redirect request with header 301, the network thread communicates with the UI thread, and a new URL request is initiated. The blog also shows how once getting the response from the server, the network checks if it's an HTML file that needs to be rendered or a zip file that needs to be downloaded (if it's then it needs to be passed to the download manager) If it's an HTML file, the network threads tell the UI thread, and then the UI thread starts a renderer process which takes care of rendering the web page. And, in last it shows what happens when you try to navigate to a different site now, and what happens in the case of the service worker. It was a nice read. It is written by Mariko Kosaka. (* find blog link in the comments *)

Firefox had separate url and search bars. This made for a safer, more straightforward, experience. One of those bars entered URLs, the other searched Google by default. Google even paid for Google logo and name on that search bar. We’ve got an abomination of “search” bars which search differently depending on where the user is in the application. Maybe I’m searching a library; maybe a help page; maybe the Internet; in a Brave Software fail, maybe I’m searching a bunch of tabs.

Soft 404 errors occur when a user accesses a URL, and the server responds with a 200 OK status code, indicating that the page exists. However, Google interprets the page as not having substantial content or being irrelevant, ideally warranting a 404 status code. Common reasons for Google to classify a page as a Soft 404 include: Creating a page but forgetting to add content. Moving content to another page without deleting the original. Page content not loading/rendering correctly due to HTML or JavaScript errors. To address Soft 404 errors, consider the following steps: Delete the page if it lacks value or purpose. Add relevant content to provide value to users if you wish to keep the page. Redirect the page to a relevant one if you moved its content elsewhere. Debug and fix any HTML or JavaScript errors affecting content loading. After implementing fixes, use Google Search Console's 'Validate Fix' feature. You'll receive notifications confirming whether the fix passed. If it fails, refine the solution and validate again to ensure proper resolution of Soft 404 errors.