Consider the following website. Page A (https://example.com/login) contains a login form and its password field has the attributes
id set to
Since the pages have the same web origin, the Same-Origin Policy does not restrict access between them and, from the browser’s view, the attacker’s code is loaded from the origin https://example.com. But the pages’ DOMs are not connected by any path that allows to access each other.
I have 54 tabs opened right now and I won’t be surprised if I open 20 more today.
I keep wondering is, can there be a way where browser assists us by giving us something that we seamlessly adopt by giving us better ways to handle our greediness towards tabs.
What is the first thing you look for when it is bottleneck situation for you to decide on closing of tabs:
-Age of the browser — How old is that, opened 2 days ago?
-Revisit the content of the tab — To make sure you are not closing anything you would be needing soon?After that, you either close it or bookmark it for later(may be).
-The sequence — Since many links open the new tab next to its previous one, wondering if same sequence (as displayed in the browser)matters.
Please feel free to add parameters that I am not factoring in.
I came across this case wherei have two tabs and under one , we have option to show save and cancel and not in other, as follows:
When you click on one member, it opens a panel that slides from right and we have save in that panel.
Please let me know if there’s problem with this flow and how to have a consistent tab navigation view.
I am designing a mobile application for enterprise , so for desktop view we are using tabs as you can see in the image below. I want to design the same for mobile, so if we use carousal tab navigation we have to swipe to reach last tab and it can be less discoverable.
- Carousal tab navigation
- Tab with more dropdown
So wanted to know if there’s any better alternative to this?
I am trying to draw out what I want to build for a new mobile app, and I’ve run into a conundrum with tabs. I have four main categories of content, and thought it would be nice to have tabs at the top users could select to get to the content they wanted quickly, as shown below. (Please excuse the crudity of my MSPaint drawing. Currently, the Users tab is selected.)
The problem I’ve run into is in my flow diagram (this is what I’m calling a diagram that shows how one page flows to the next, looked at from a user perspective). Let’s say I have content on the Users tab, and I want to add a screen that allows me to add a New User or a screen that that allows me to update an existing user’s information. I had thought I would just do a pop up if they clicked on an existing users’s name (or New User), but I’m starting to wonder if tabs and popups don’t mix well.
I definitely don’t want to have different breadcrumbs for each tab, as I think that would be terribly hard to navigate. So the root of my question is: what is a common guideline for having more than one screen per tab? Or should I abandon tabs entirely? Each of these 4 tabs could have more than one screen.
I have several queries in the editor, each terminating with a semi-colon (I am teaching myself SQL and so in the editor is a mix of queries and notes like below):
SELECT * FROM orders WHERE order_date >= ‘2019-01-01’;
— AND operator
SELECT * FROM customers WHERE birth_date > ‘1990-01-01’ AND points > 1000;
— OR operator
SELECT * FROM customers WHERE birth_date > ‘1990-01-01’OR points > 1000 AND state = ‘VA’;
— NOT operator
— Exercise: FROM order_items table get the items — for order #6 — where total price is greater than 30
SELECT * FROM order_items WHERE order_id = 6 AND quantity * unit_price >= 30;
When I first began using MYSQL, I would run a query and only the last SELECT statement would run and the results would show in the result tab. The ACTION OUTPUT would show the time-stamp which clearly indicated only the last SELECT statement in the editor was run.
Now, all queries ending with a semi-colon are running simultaneously and each appears on its own tab and in the ACTION OUTPUT section on the bottom (i.e., “orders43”, “customers44”, “customers45” and so on.)
The only way I can get the most recent result is by highlighting the specific SELECT statement and running the query. However, I want to know why the results aren’t just “overriding” each other and the most recent SELECT statement being the results displayed in the same result tab…
At this rate, I’ll have hundreds of result tabs for each query ending with a semi-colon, and this is clearly not what I want nor was it how the workbench was working for me up until recently.
I am not sure why this is occurring, or how to stop it.
Any help would be greatly appreciated.
In a page we’re designing, we have an issue of there being two tabs (closely positioned) and I wanted some suggestions for alternatives. Essentially in this page, we have a main tab that serves the function of switching between different tables. This function can’t be changed but can be displayed differently (drop down wasn’t working out). The second tab appears when the user clicks a button on the screen, and a slider opens up into half of the table. In this slider there is another set of tabs. Do you all have any suggestions as to how to maneuver this? Sorry if I’m being unclear, let me know if I can help clarify. I have attached an image for context.
We are trying to provide users with a strong filter mechanism on a Dashboard that collects visit data. It feels like we have arrived at a point where only a few pieces of the puzzle are missing and we don’t know how to place them.
The user should be able to:
- Define the filter parameters.
- Save them for future use along with a name.
- Apply them for one-time use to quickly check or search something without the need for saving them.
- Modify the parameters of an existing saved filter and save it again.
- Open tabs in the software itself and apply different filters (saved and unsaved) to easily switch from one type of data to another.
- Close tabs.
There is a live view tab that is static and can’t be modified or removed by the user. (Mentioned from now on as the default tab)
Solution: (So far) 1. A filter button on the dashboard that opens a side panel for filters that contains all the parameters and allows the user to save a filter, save as existing or just apply.
A Tab System that works like you’d expect. It allows the user to change the filter applied in a tab by clicking on a drop-down icon on the right side of the tab itself and selecting from the saved filters list.
A plus button at the end of the tab list which works exactly like the drop-down above, prompting the user to select which filter view to apply on the new tab avoiding any empty states or empty tabs open.
Points we still can’t seem to get a grip on:
How to make the experience of applying a filter to any open tab as seamless as possible? For example, if the user is on a tab and he clicks on the Filters button and changes some parameters and clicks Apply. Should we update the view to Unsaved View? Should we keep the name of the tab same with an asterisk to denote unsaved state with a reset button? Or should we open a new tab (potentially leading to a lot of unsaved tabs open?)
If subsequently, he refreshes his page? Should the unsaved view disappear (being unsaved) or should we keep it in memory (potentially not really creating a need to use the ‘Save Filter’ feature)
How to treat the default tab in all this? Should we disable all filtering options in the default tab to avoid any confusion leading to some loss in discoverability of filter features that are available as they will not show in the default tab or should we show filtering options on the default tab and open any changes made on the default tab in a new tab leading to a little bit of inconsistency (changing any filters from the default tab always opens a new tab while changing any filters from other tabs only makes changes to that specific tab and then implementing a fail safe or an error state if the user tries to make changes to the default tab with the maximum limit reached)
Creating a responsive design around the solution.
It’ll be great to get insights and thought process on how to go about this problem.
Firefox 69.0.1 on Ubuntu: How does one save a group of tabs as single line-item? It would be very useful to be able to recall the saved group in a future browsing session.
I have a page with tabs. The
Save Data will save data for all tabs. It is possible that some tabs will have input fields that will be invalid when they hit save.
How would I go about handling invalid fields? For instance, the user could hit save while on a different tab and be confused why it’s not saving.