Apple proposes improvements to Safari browsing experience
A pair of new patent filings from Apple include suggestions for improving the browsing experience offered through its Safari Web browser, such as a adaptive media support and a visual history tree that more accurately shows users where they've been and how they got there.
Both filings are relatively fresh, having been filed in January and April of this year, respectively, and each are credited to known members of the Cupertino-based company's Mac OS technology and QuickTime teams.
Viewing histories as tree diagrams
Of particular interest is the filing for improved navigation history display, which suggests that a user's browser history be presented in the form of a visual tree diagram tied to a timeline, rather than as a linear list of previously accessed pages that otherwise lacks structure.
"A problem with this linear history is that users can visit a large number of web pages, which are confusing to view in a linear history, and the forward and back buttons are inefficient and cumbersome way to navigate through multiple web pages," Apple said. "Further, the problems of a linear history are not confined to pages accessed via a web browser, but also apply when a succession of data of other types is accessed over a period of time."
To remedy these issues, the company proposes a signal-bearing medium where previously-accessed web pages are displayed as nodes in a tree (or trees) alongside an axis representing time.
Under this model, the root node of a tree would represent a webpage accessed manually when the user enters an address into Safari's address bar, while a child node of the tree would represent pages later selected from the parent node. The tree would split each time the user spawns a new window or tab and represent this split to the user through variations in the lines connecting the tree nodes.
The new history interface would also include controls for scaling the tree by time of depth, as it's likely that users will visit a large number of web pages during any given session.
"Compression reduces the number of displayed nodes by only displaying, for example, nodes associated with pages that have an address with a hierarchical level corresponding to the position of the depth slider," Apple said. "When the depth is set at zero compression, all nodes are displayed. When the depth is set at maximum compression, only nodes associated with an address at the first hierarchical level are displayed."
Adaptive media support
In the second filing, Apple looks to solve the problem where Mac users are sometimes prevented from viewing digital media -- primarily videos -- on the Web because Safari lacks the means required for display of that media in its preferred format.
"In web browsers other than Internet Explorer, it is up to the Web browser to find a registered plug-in for use based on the media type specified in the HTML," Apple wrote in the filing. "In these examples, a Web browser must either determine whether there is an appropriate plug-in or must use a single specified plug-in which may not be available. If it is not available, the media content cannot be displayed or otherwise presented."
As a solution, the company proposes that Safari examine metadata included with the media item to determine whether the content can be displayed in an alternative format supported natively by the browser, or through plug-ins that could retrieved and installed on the spot.
"The preferred from or representation may be specified first and examined first and if the user agent is not able to support the preferred form, then the user agent may examine the rest of the tag or metadata to determine what other forms or representations it can support," the filing says. "The other forms or representations may be characterized as fallback positions or forms. In addition, the tag or metadata may specify other parameters or conditions, such as bandwidth or data rates, which can be used to select which form of the content to present."
Both filings are relatively fresh, having been filed in January and April of this year, respectively, and each are credited to known members of the Cupertino-based company's Mac OS technology and QuickTime teams.
Viewing histories as tree diagrams
Of particular interest is the filing for improved navigation history display, which suggests that a user's browser history be presented in the form of a visual tree diagram tied to a timeline, rather than as a linear list of previously accessed pages that otherwise lacks structure.
"A problem with this linear history is that users can visit a large number of web pages, which are confusing to view in a linear history, and the forward and back buttons are inefficient and cumbersome way to navigate through multiple web pages," Apple said. "Further, the problems of a linear history are not confined to pages accessed via a web browser, but also apply when a succession of data of other types is accessed over a period of time."
To remedy these issues, the company proposes a signal-bearing medium where previously-accessed web pages are displayed as nodes in a tree (or trees) alongside an axis representing time.
Under this model, the root node of a tree would represent a webpage accessed manually when the user enters an address into Safari's address bar, while a child node of the tree would represent pages later selected from the parent node. The tree would split each time the user spawns a new window or tab and represent this split to the user through variations in the lines connecting the tree nodes.
The new history interface would also include controls for scaling the tree by time of depth, as it's likely that users will visit a large number of web pages during any given session.
"Compression reduces the number of displayed nodes by only displaying, for example, nodes associated with pages that have an address with a hierarchical level corresponding to the position of the depth slider," Apple said. "When the depth is set at zero compression, all nodes are displayed. When the depth is set at maximum compression, only nodes associated with an address at the first hierarchical level are displayed."
Adaptive media support
In the second filing, Apple looks to solve the problem where Mac users are sometimes prevented from viewing digital media -- primarily videos -- on the Web because Safari lacks the means required for display of that media in its preferred format.
"In web browsers other than Internet Explorer, it is up to the Web browser to find a registered plug-in for use based on the media type specified in the HTML," Apple wrote in the filing. "In these examples, a Web browser must either determine whether there is an appropriate plug-in or must use a single specified plug-in which may not be available. If it is not available, the media content cannot be displayed or otherwise presented."
As a solution, the company proposes that Safari examine metadata included with the media item to determine whether the content can be displayed in an alternative format supported natively by the browser, or through plug-ins that could retrieved and installed on the spot.
"The preferred from or representation may be specified first and examined first and if the user agent is not able to support the preferred form, then the user agent may examine the rest of the tag or metadata to determine what other forms or representations it can support," the filing says. "The other forms or representations may be characterized as fallback positions or forms. In addition, the tag or metadata may specify other parameters or conditions, such as bandwidth or data rates, which can be used to select which form of the content to present."
Comments
The second seems blatantly obvious.
I've been trying to keep my system running lean, mean and clean and Safari has been crashing like never before since the 10.5.4 update. I just jumped on board 10.5.5 yesterday so I haven't been able to see if that has made a difference, but has anyone else noticed Safari being buggier than usual?
If I were to pick which Safari problem I could have I would rather have the memory leak that caused jumpy page scrolling/lag than the amount of crashes I've been having.
"the user agent may examine the rest of the tag or metadata to determine what other forms or representations it can support," the filing says.
yes it does seem obvious.
And at the same time.. it makes me think Apple wants Quicktime to play Flash videos natively... and wants safari to help.
I would just like Safari to be more stable and not start spitting and sputtering when it doesn't like something on a webpage.
I've been trying to keep my system running lean, mean and clean and Safari has been crashing like never before since the 10.5.4 update. I just jumped on board 10.5.5 yesterday so I haven't been able to see if that has made a difference, but has anyone else noticed Safari being buggier than usual?
I've noticed everything from Apple seems to get a bit more buggier with every release they do. Like the way they've also removed the bit from there reasons to get a mac page that used to say "It just works" as obviously it now doesn't.
... Safari has been crashing like never before since the 10.5.4 update. I just jumped on board 10.5.5 yesterday so I haven't been able to see if that has made a difference, ....
I work at a large all mac place that hasn't seen any of the problems you talk about, but you are right about the updates.
In any troubleshooting attempt, the very first step is to make sure all the software is up to date. it's not even worth thinking about a problem, let alone talking about it, if you haven't first ensured that you have all the latest software, patches, bug-fixes etc.
Another good rule of thumb is that some (insert huge made up percentage here), of browser "problems" usually turn out to be web page problems. For instance if a browser is "stuttering" that suggests it's stuck in a loop or trying to load the same info over and over again. That kind of crap behaviour is so extremely unlikely on any modern browser that it's almost certainly a problem with the way the site is coded.
Apple need to stop trying to expand their self too much within a year and focus back on their quality. We dont want to see Microsoft No.2
Can we finally please get the option to not view the address bar like every other browser has ( view web pages full screen)?
1) Hide Toolbar
2) Customize ToolBar, then remove the Address Bar.
...but I'm sure you'll complain about these options.
I would just like Safari to be more stable and not start spitting and sputtering when it doesn't like something on a webpage.
I've been trying to keep my system running lean, mean and clean and Safari has been crashing like never before since the 10.5.4 update. I just jumped on board 10.5.5 yesterday so I haven't been able to see if that has made a difference, but has anyone else noticed Safari being buggier than usual?
If I were to pick which Safari problem I could have I would rather have the memory leak that caused jumpy page scrolling/lag than the amount of crashes I've been having.
Don't you know it's not Safari/Apple's problem being unstable - it's just the web designers fault?
1) Hide Toolbar
2) Customize ToolBar, then remove the Address Bar.
...but I'm sure you'll complain about these options.
A.) It shouldn't be that difficult- a one click solution would suffice -like every other browser has.
B.) Did you wake up on the wrong side of the bed?
A.) It should't be that difficult- a one click solution would suffice -like every other browser has.
B.) Did you wake up on the wrong side of the bed?
⌘+Shift+| or remap it to something simpler.
It seems to me that the tree history would make more intuitive sense if the "root" was at the bottom of the page. That puts where you started at the bottom, and where you are now at the top. I usually want to start with where I am and work back. If I need to get to the root I can always click the SnapBack orange arrow in the address bar. I don't know if this tree thing is the best solution, but I find the current history implementation kinda one point oh. It's nice to know they're at least thinking about it.
Naah.
⌘+Shift+| or remap it to something simpler.
Touché
It seems to me that the tree history would make more intuitive sense if the "root" was at the bottom of the page. That puts where you started at the bottom, and where you are now at the top. I usually want to start with where I am and work back. If I need to get to the root I can always click the SnapBack orange arrow in the address bar. I don't know if this tree thing is the best solution, but I find the current history implementation kinda one point oh. It's nice to know they're at least thinking about it.
Why not just make it similar to the TimeMachine UI.
It basically does the exact same thing.
⌘+Shift+| or remap it to something simpler.
Kinda makes you wonder why he picked the alias "techstud" doesn't it.
Apple really ought to buy Inquisitor - that'd make a great addition to Safari.
Too bad Yahoo! beat them to it.